stackabletech / stackabletech/superset-operator
Don't require adminUser when LDAP support is used
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 35
- Forks
- 4
- Avg merge
- 12h 20m
- Merged PRs (30d)
- 10
Description
Currently we require to specify an adminUser (like below) in any case.
If we enable LDAP the adminUser is not able to log in - it's basically disabled. So we should somehow manage think about that
adminUser.username: admin
adminUser.firstname: Superset
adminUser.lastname: Admin
adminUser.email: admin@superset.com
adminUser.password: admin
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
Start by locating the operator entry points that handle the adminUser configuration and LDAP support described in the issue. Determine how configuration behaves when LDAP is enabled, then verify that deployments using LDAP no longer require a usable adminUser while other authentication setups retain their current behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- authentication, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100