Simplify local CDA GUI authentication
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 28
- Forks
- 25
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 20
Description
Follow-up to #1865 and this review comment.
We should let Docker Compose use the runtime OpenAPI configuration and normal redirect-based login instead of the hard-coded direct-grant user. For standalone ./gradlew run, add a simple API-key path for cases where Keycloak is not available.
Contributor guide
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 tracing the Docker Compose authentication setup and the standalone ./gradlew run entry point, including how runtime OpenAPI configuration and the current direct-grant user are wired. Done means Compose uses redirect-based login with runtime configuration, while standalone runs have an API-key path when Keycloak is unavailable; add or update focused tests if the existing authentication test locations reveal them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, java, openapi
- Domain
- api, authentication, devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100