-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✨ 💥 Add Authentication and ACLs #20
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…-dir` and `-config` CLI flag to `-config-dir`
… be done in a later feature
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Decision Record
Access Control is an important part of any software dealing with potentially secret data (in this case, system logs).
Design
FlowG will use a Role Based Access Control design (RBAC for short). Each role will assign permissions to a specific scope. The following scopes has been identified:
read_pipelines
write_pipelines
read_transformers
write_transformers
read_streams
write_streams
read_acls
write_acls
send_logs
Each user is associated to one or more roles. A user has a required password, and can have zero or more personal access tokens.
The user password will be used to login to the Web UI, while the personal access tokens will be used to access the API.
Implementation
Passwords and Personal Access Tokens will be hashed using Argon2.
The authentication system will use a separate BadgerDB database to store users and roles.
Changes
License Agreement