stackabletech / stackabletech/druid-operator
Authorization withouth an authenticator - how does it work?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 12
- Forks
- 1
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 10
Description
It's easy to get confused when you enable authorization and nothing happens - no warnings, but also no functional authorization. (Custom overrides are necessary to point to the authorizer)
If would be great to emit an error, stating that an authentication method seems to be missing.
Possible addition: this behaviour could be overridden with a custom config flag, allowing the user to specify their own authentication via config overrides if desired. Preventing non-functional authorization would help for a transparent and intuitive user experience.
Related: TLS authentication can currently not be connected to authorization it seems?
Update: work with an anonymous authenticator?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing the operator's authorization and authenticator configuration, including TLS and anonymous authentication; done means the expected missing-authenticator behavior and any configuration override are agreed and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- authentication, authorization, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100