Externalize authentication to keycloak
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 16
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Description
We want to externalize authentication to keycloak for several reasons:
- Keycloak may also be used to authenticate users with MinIO. This should allow for easier configuration of private objects (datasets, runs, ...), as we don't need to duplicate our user information between MinIO and the main server.
- The less sensitive information we store, the better.
- The less code we maintain, the better. This allows us features like expiring tokens without additional code on our end.
This is required for the migration, as we do not plan to support private datasets on MinIO without it. However, we currently plan to tackle this only after all the other migration work is done.
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 reviewing the server's current authentication flow and the migration work referenced in the issue, then examine how MinIO access is configured. Done means authentication is externalized to Keycloak and private MinIO datasets and related objects can use the shared user information without duplicated authentication data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100