Keycloak support in Angular #37234
Unanswered
AnandKatta
asked this question in
Q&A
Replies: 2 comments
|
hi @jonkoops, please share your thoughts. Even on token exchange endpoint for the getting new token using access token, scopes are omitted. New access token generated from token exchange, is the same scope which we send in the access token |
0 replies
|
hi team, Any update on this question |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Before reporting an issue
Area
docs
Describe the bug
Hi team,
We plan to migrate from msal from azure ad in angular to use Keycloak as identity broker and azure ad as identity provider.
Please let us know, which packages is recommended/supported by keycloak team to use it in angular.
I am currently using keycloak-angular in Angular17.
After logging in into the my application using keycloak with check-sso. I have different clients in my application. When i switch the client, i need to get a new access for the same front clientid with different scope(specific to the client). Basically this scope will return corresponding roles for that client in keycloak. I am using "/realms//protocol/openid-connect/token" with grant_type="refresh_token". But still it return the token with same scope as, while login In. Do i need to use token exchange approach?. Here the token generation should be same client but on different scopes. Please help me to address this. Thanks a lot.
Version
24.0.1
Regression
Expected behavior
I can able to generate a new access token with different scope for the same client using grant_type as refresh_token
Actual behavior
Newly generated access token containing the same scope.
How to Reproduce?
Generate a token using authorization code flow, Using the generated refresh token, request a new access token with different scope with grant_type as "refresh_token"
Anything else?
No response
All reactions