Giter Club home page Giter Club logo

auth's People

Contributors

petehayes102 avatar rushmorem avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar

auth's Issues

Certificate store permissions

installer.sh should set more aggressive default permissions for the certificate store directory (<sysconfdir>/intecture/certs), and ensure it is owned by root.

Upload to crates.io

  • Remove GitHub dependencies from Cargo.toml
  • Check metadata in Cargo.toml
  • Update other projects to reference crates.io when including this lib as a dependency

Process does not respect SIGTERM

This is likely due to a child thread loop that does not get told to terminate. In this case, a ZMQ pipe should be used to send a $TERM signal to the child thread when the parent's drop() fn is called.

Default to ports 7103, 7104

By defaulting Auth to 7103 and 7104, it will eliminate potential port clashes with Agent, standardise the configuration and simplifies the user story.

Auth CLI should call API to add certificates

Currently when the Auth CLI creates a new certificate, it adds it directly to the disk store. This means that the Auth server is unaware of the certificate until the daemon is restarted, resulting in much confusion among users!

Instead, the CLI should wrap the ZMQ API so that it is published as soon as it's created. If this fails, it can fall back to the current behaviour with a warning that it couldn't connect to the API:

WARNING: Could not connect to the API to register this certificate, which either means that the Auth daemon is not running, or there's a connectivity issue. If the daemon is running, please restart it to register this certificate.

Create init scripts for daemon

In order to properly daemonise the process, it needs to have an init script to look after starting/stopping/restarting the process, recording the PID etc.

Must support:

  • Upstart
  • Systemd
  • BSD init
  • MacOS launchd

This issue is blocked by #1.

Document steps for building and configuring manually

The book mentions that you can compile from source using make. This is great. However, it would even be better if we also have instructions on how to build and configure manually without using the Makefile. Specifically, mention:-

  • cargo build --release,
  • and how to setup /etc/intecture

so commands like inauth_cli user add <username> can just work out of the out of the box.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.