Skip to content
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

boardwalkd API authentication #4

Closed
m4wh6k opened this issue Oct 11, 2022 · 1 comment
Closed

boardwalkd API authentication #4

m4wh6k opened this issue Oct 11, 2022 · 1 comment
Labels
enhancement New feature or request
Milestone

Comments

@m4wh6k
Copy link
Contributor

m4wh6k commented Oct 11, 2022

Currently, the boardwalkd server has at least one built-in UI authentication method (Google Oauth2) available. There isn't yet any API authentication method available, and we should have one.

My current thinking is that there should be an "API Keys" management page in the UI, where users can create and delete API keys that can be used to authenticate to the API from boardwalk CLI workers. There should be a way to name API keys and see when they were last used.

The boardwalk CLI will need to be updated to support supplying an API key as well.

Authorization is out of scope for now. Currently being authenticated to the boardwalkd server simply provides full access, and this will still be true for this initial API authentication scheme.

@m4wh6k m4wh6k added the enhancement New feature or request label Oct 11, 2022
@m4wh6k m4wh6k self-assigned this Oct 11, 2022
@m4wh6k m4wh6k added this to the 1.0.0 milestone Oct 11, 2022
@m4wh6k
Copy link
Contributor Author

m4wh6k commented Oct 31, 2022

This was fixed by #17, although implemented differently than described above.

There's more work needed to be done to expand on this, see #18 and #19

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant