Support for client credentials security check in micronaut controllers
Open
Nobody has claimed this yet.
design discussion required
hacktoberfest
- Dominant language
- Kotlin
- Stars
- 4
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Problem:
Currently defining a security scheme for client credentials flow in open api spec yml doesn't translate to any security checks in micronaut controllers.
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 how the OpenAPI security scheme is translated into generated Micronaut controllers, focusing on the client credentials flow. Done means a client credentials scheme declared in the OpenAPI YAML results in the corresponding controller security checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, openapi
- Domain
- api, authentication, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100