-
Notifications
You must be signed in to change notification settings - Fork 7
feat(IPROD-189-3): used Keycloak to perform /login action to do OAuth 2.0 authorization code flow #83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
….0 authorization code flow
|
lgtm so far, fix checks and I can approve. was there some reason we couldn't of used some library for this? |
…after login from root route)
mdebarros
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some suggested wording changes.
Please let me know if you agree with the changes.
Co-authored-by: Miguel de Barros <[email protected]>
Co-authored-by: Miguel de Barros <[email protected]>
mdebarros
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
We need to use Keycloak to authenticate users to follow OAuth 2.0 authorization code flow for MCM layer (hub operator)
Env variables:
AUTH_ENABLEDis disabled by default (previous auth flow)UI_OIDC_LOGIN_REDIRECT_URL- URL to redirect user to provide creds and grand permissions (Keycloack)OIDC_TOKEN_PROVIDER_URL- URL to exchange authorization code for access token (providing also client ID and secret)OIDC_CLIENT_ID- MCM portal OIDC client id (in Keycloak)OIDC_CLIENT_SECRET- MCM portal OIDC client secret (in Keycloak)