Repository navigation
Authorization services not work #20779
Unanswered
MorganReid
asked this question in
Q&A
Replies: 2 comments 3 replies
|
Same issue for me |
1 reply
|
Ok I think I solved the issue, in keycloak, when authorization is being done, keycloak doesn't stop the user from signing in ever, instead what it does is in the OpenID Connect token being given, it includes a new claim about which resources the user should be allowed to access, this is up to the application to interpret, not keycloak. If your application does not understand how to restrict certain users from logging in based on authorization, you can create a custom flow that checks for a claim and then denies access at the keycloak level. That would however require some more additional steps. Tell me if you want me to tell you how to do that. |
2 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.
I want to implement a client to only open permissions to specified users, and complete the configuration through official documents, but it does not take effect.






client capability config:client Authorization Resource:client Authorization policy:Create a new policy namedmypolicywhoseTypeisUser, and specify userwiki1client Authorization permission:Create a new permission whoseTypeisResource-Based, and specify policymypolicy,specific resourcesDefault Resourcewhen i use
Evaluatetest,looks as expecteduse wiki1:
use wiki2:
But when I access my client(
OpenID Connect), it will use keycloak for login authentication. Both wiki1 and wiki2 can be authenticated.Is there any configuration I'm missing? hope you can help me.All reactions