Determine from JWT generated by Keycloak if a user is authorized to access specific resource
Keycloak docs on OpenID Connect states that
The access token is digitally signed by the realm and contains access
information (like user role mappings) that the application can use to
determine what resources the user is allowed to access on the
application.
Is it possible to determine from the access token returned by Keycloak after authentication what resources a user is allowed to access?
Following the keycloak quickstart's instructions on Obtaining an OAuth2 Access Token, i get the following JWT (with not relevant fields ommitted) :
{
"aud": "app-authz-springboot",
"sub": "9c6c4a66-bb14-420f-a8af-3b2771266b38",
"typ": "Bearer",
"azp": "app-authz-springboot",
"realm_access": {
"roles": [
"user"
]
},
"resource_access": {},
"preferred_username": "alice"
}
There's an empty field
resource_access
Is there any way to fill it with the resources a user has access to? What's the specification of this field? Couldn't find it in JWT RFC or OpenID Connect Spec
I attempted another way that worked:
- Obtaining the access token using password credentials flow
Exchanging the obtained token for rpt with slight
modification adding response_mode argument:
curl -v -X POST
http://localhost:8180/auth/realms/spring-boot-quickstart/protocol/openid-connect/token
-H "Authorization: Bearer "$access_token
--data "grant_type=urn:ietf:params:oauth:grant-type:uma-ticket"
--data "audience=app-authz-rest-springboot"
--data "permission=Default Resource"
--data "response_mode=decision"
However this solution requires dispatching 2 requests to Keycloak to determine if a user is allowed a specific resource.
oauth-2.0 authorization jwt openid-connect keycloak
add a comment |
Keycloak docs on OpenID Connect states that
The access token is digitally signed by the realm and contains access
information (like user role mappings) that the application can use to
determine what resources the user is allowed to access on the
application.
Is it possible to determine from the access token returned by Keycloak after authentication what resources a user is allowed to access?
Following the keycloak quickstart's instructions on Obtaining an OAuth2 Access Token, i get the following JWT (with not relevant fields ommitted) :
{
"aud": "app-authz-springboot",
"sub": "9c6c4a66-bb14-420f-a8af-3b2771266b38",
"typ": "Bearer",
"azp": "app-authz-springboot",
"realm_access": {
"roles": [
"user"
]
},
"resource_access": {},
"preferred_username": "alice"
}
There's an empty field
resource_access
Is there any way to fill it with the resources a user has access to? What's the specification of this field? Couldn't find it in JWT RFC or OpenID Connect Spec
I attempted another way that worked:
- Obtaining the access token using password credentials flow
Exchanging the obtained token for rpt with slight
modification adding response_mode argument:
curl -v -X POST
http://localhost:8180/auth/realms/spring-boot-quickstart/protocol/openid-connect/token
-H "Authorization: Bearer "$access_token
--data "grant_type=urn:ietf:params:oauth:grant-type:uma-ticket"
--data "audience=app-authz-rest-springboot"
--data "permission=Default Resource"
--data "response_mode=decision"
However this solution requires dispatching 2 requests to Keycloak to determine if a user is allowed a specific resource.
oauth-2.0 authorization jwt openid-connect keycloak
add a comment |
Keycloak docs on OpenID Connect states that
The access token is digitally signed by the realm and contains access
information (like user role mappings) that the application can use to
determine what resources the user is allowed to access on the
application.
Is it possible to determine from the access token returned by Keycloak after authentication what resources a user is allowed to access?
Following the keycloak quickstart's instructions on Obtaining an OAuth2 Access Token, i get the following JWT (with not relevant fields ommitted) :
{
"aud": "app-authz-springboot",
"sub": "9c6c4a66-bb14-420f-a8af-3b2771266b38",
"typ": "Bearer",
"azp": "app-authz-springboot",
"realm_access": {
"roles": [
"user"
]
},
"resource_access": {},
"preferred_username": "alice"
}
There's an empty field
resource_access
Is there any way to fill it with the resources a user has access to? What's the specification of this field? Couldn't find it in JWT RFC or OpenID Connect Spec
I attempted another way that worked:
- Obtaining the access token using password credentials flow
Exchanging the obtained token for rpt with slight
modification adding response_mode argument:
curl -v -X POST
http://localhost:8180/auth/realms/spring-boot-quickstart/protocol/openid-connect/token
-H "Authorization: Bearer "$access_token
--data "grant_type=urn:ietf:params:oauth:grant-type:uma-ticket"
--data "audience=app-authz-rest-springboot"
--data "permission=Default Resource"
--data "response_mode=decision"
However this solution requires dispatching 2 requests to Keycloak to determine if a user is allowed a specific resource.
oauth-2.0 authorization jwt openid-connect keycloak
Keycloak docs on OpenID Connect states that
The access token is digitally signed by the realm and contains access
information (like user role mappings) that the application can use to
determine what resources the user is allowed to access on the
application.
Is it possible to determine from the access token returned by Keycloak after authentication what resources a user is allowed to access?
Following the keycloak quickstart's instructions on Obtaining an OAuth2 Access Token, i get the following JWT (with not relevant fields ommitted) :
{
"aud": "app-authz-springboot",
"sub": "9c6c4a66-bb14-420f-a8af-3b2771266b38",
"typ": "Bearer",
"azp": "app-authz-springboot",
"realm_access": {
"roles": [
"user"
]
},
"resource_access": {},
"preferred_username": "alice"
}
There's an empty field
resource_access
Is there any way to fill it with the resources a user has access to? What's the specification of this field? Couldn't find it in JWT RFC or OpenID Connect Spec
I attempted another way that worked:
- Obtaining the access token using password credentials flow
Exchanging the obtained token for rpt with slight
modification adding response_mode argument:
curl -v -X POST
http://localhost:8180/auth/realms/spring-boot-quickstart/protocol/openid-connect/token
-H "Authorization: Bearer "$access_token
--data "grant_type=urn:ietf:params:oauth:grant-type:uma-ticket"
--data "audience=app-authz-rest-springboot"
--data "permission=Default Resource"
--data "response_mode=decision"
However this solution requires dispatching 2 requests to Keycloak to determine if a user is allowed a specific resource.
oauth-2.0 authorization jwt openid-connect keycloak
oauth-2.0 authorization jwt openid-connect keycloak
edited Nov 22 at 14:18
Lukasz Stelmach
4,20031828
4,20031828
asked Sep 26 at 10:04
user1264304
95562253
95562253
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Your usage scenario is not clear. The standard mechanism to control access to specific resources is roles and you do get them as a part of the token. So if you configure access to your endpoints using appropriate roles model and assign required roles to the corresponging users, it will control the access. Actually this is the way access to the /api/premium
URL is managed in the SpringBoot example that you referencing in your question (compare access by alice vs jdoe).
From your question as it is now, it is not clear why such approach doesn't work for you and why you want something else.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52515135%2fdetermine-from-jwt-generated-by-keycloak-if-a-user-is-authorized-to-access-speci%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Your usage scenario is not clear. The standard mechanism to control access to specific resources is roles and you do get them as a part of the token. So if you configure access to your endpoints using appropriate roles model and assign required roles to the corresponging users, it will control the access. Actually this is the way access to the /api/premium
URL is managed in the SpringBoot example that you referencing in your question (compare access by alice vs jdoe).
From your question as it is now, it is not clear why such approach doesn't work for you and why you want something else.
add a comment |
Your usage scenario is not clear. The standard mechanism to control access to specific resources is roles and you do get them as a part of the token. So if you configure access to your endpoints using appropriate roles model and assign required roles to the corresponging users, it will control the access. Actually this is the way access to the /api/premium
URL is managed in the SpringBoot example that you referencing in your question (compare access by alice vs jdoe).
From your question as it is now, it is not clear why such approach doesn't work for you and why you want something else.
add a comment |
Your usage scenario is not clear. The standard mechanism to control access to specific resources is roles and you do get them as a part of the token. So if you configure access to your endpoints using appropriate roles model and assign required roles to the corresponging users, it will control the access. Actually this is the way access to the /api/premium
URL is managed in the SpringBoot example that you referencing in your question (compare access by alice vs jdoe).
From your question as it is now, it is not clear why such approach doesn't work for you and why you want something else.
Your usage scenario is not clear. The standard mechanism to control access to specific resources is roles and you do get them as a part of the token. So if you configure access to your endpoints using appropriate roles model and assign required roles to the corresponging users, it will control the access. Actually this is the way access to the /api/premium
URL is managed in the SpringBoot example that you referencing in your question (compare access by alice vs jdoe).
From your question as it is now, it is not clear why such approach doesn't work for you and why you want something else.
answered Nov 22 at 21:02
SergGr
18.8k22243
18.8k22243
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52515135%2fdetermine-from-jwt-generated-by-keycloak-if-a-user-is-authorized-to-access-speci%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown