theopenconversationkit / theopenconversationkit/tock
[Studio OIDC & KeyCloak] Scopes requested at login stage are hardcoded
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 612
- Forks
- 156
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 9
Description
When OIDC (OAuth2Provider or KeycloakOAuth2Provider) is used to authenticate users, scope lists asked during authentication are not defined, so, it seems that one used per default is :
- openid
- profile
Scopes are useful to get user information and map them to Tock roles.
It could be cool to have a property, for example, for keycloak tock keycloak scopes with default values (openid profile email) that can let the Ops define needs scopes.
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 locating the OAuth2Provider and KeycloakOAuth2Provider authentication entry points and inspect how the default openid, profile, and email scopes are selected. Done means Ops can configure the requested scopes, while those three values remain the defaults when no property is provided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100