[keycloak-user] Restrict access from web app client

Fri Aug 18 05:00:46 EDT 2017

Thanks Simon,

Yes, I think we're getting closer. To avoid confusion, let me rename the
originating client "A" and the resource client "B".

Answer in-line:

On 17/08/17 17:05, Simon Payne wrote:
> Hi, i'm not sure i follow your use case then.  I read your question to mean
> 'how to restrict a resource server to only validating a token to tokens
> requested by white listed clients.'
It's almost right, but just inside Keycloak (so, without touching the
client A itself or the resource server behind client B.)

> audience is keycloak defaults to the client id if not specified.  you can
> override this to whatever you want by adding to the mappers tab.

I was taking a look at the different types of Mappers for client A and
did not find one for the audience. What kind of mapper should one use?
Hardcoded claim? Then, the claim should be called 'aud', right?
(I am doing everything through the web interface, btw)

But then, if I do it this way, I will have to change each resource
server, right?

> re-reading your email however, it sounds like scope or roles might be your
> solution.  after adding the roles to either the user or service account
I could add the role to the client A without using service accounts, right?

> then you need to add the relevant authorization to each client in the
> property file, mapping the resource to the role required. e.g. (springboot)
>
> keycloak.realm = master
> keycloak.auth-server-url = xxxxx
> keycloak.ssl-required = external
> keycloak.resource = xxxxxx
> keycloak.credentials.secret=xxxxxx
> keycloak.bearer-only= true
>
> keycloak.security-constraints[0].authRoles[0] = user
> keycloak.security-constraints[0].securityCollections[0].name = resources
> keycloak.security-constraints[0].securityCollections[0].patterns[0] = /*
>
> keycloak.security-constraints[1].authRoles[0] = super_user
> keycloak.security-constraints[1].securityCollections[0].name = secure resources
> keycloak.security-constraints[1].securityCollections[0].patterns[0] = /products

I understand you are refering to client B, right? Anyway, I don't find
anywhere to change the property file from the web gui. I tried creating
a new "auth-scope" in the Authorization section of client B, assigned it
to the Default Resource, assigned them all to the Default Permission and
all to the Default Policy (the one I defined with JS as for my first
email: if (contextAttributes.containsValue('kc.client.id',
'simplewebapp')) {    $evaluation.deny(); }

(BTW simplewebapp is client A)

No luck :( am I doing something wrong?

(I did not force any role on client A, and policy is set to Enforcing)

> Alternatively you can make use of the authorization services to achieve the
> same thing, but must enable at the client by using
> keycloak.policy-enforcer-config.enforcement-mode=ENFORCING  I noticed that
> before the auth services would work i also had to include client side
> mapping of the minimum level of authorization.
I guess here you are also speaking about client B, right?

I did not understand what you mean by client side mapping of the minimum
level of authorization. What client mapping? Are there levels of
authorization?

Thanks a lot for your help!
BR/Pablo

>
>
> Hope this helps,
>
> Simon.
>
>
>
>
>
>
> On Thu, Aug 17, 2017 at 7:36 AM, Pablo Fernandez <pablo.fernandez at cscs.ch>
> wrote:
>
>> Dear Simon,
>>
>> Thanks for your reply.
>>
>> I am not quite sure your proposal would work in our case (or maybe I
>> don't understand it): do you mean that the client will ask for a
>> specific audience to be put inside the token, and that the other service
>> providers would have to check that the claim is targeted against the
>> right audience? That creates a big overhead if you have many SPs, which
>> we do. And anyway, how can you limit a certain client to be issued token
>> of a certain audience within Keycloak? And furthermore, how can I limit
>> the access to the /accounts API on Keycloak for a token given to certain
>> clients?
>>
>> It would be great to have a mechanism inside Keycloak to limit the
>> scopes of the various clients directly, without extra work on the
>> clients or the SPs. Am I assuming something that is wrong? What is the
>> Authorization tab (and/or the Scopes one) for?
>>
>> Thanks a lot again,
>> BR/Pablo
>>
>>
>> On 16/08/17 15:20, Simon Payne wrote:
>>> Pablo,
>>>
>>> i'm not sure whether this will be your solution directly, but i found out
>>> recently that the 'aud' claim in the token is to represent the audience.
>>> Now, when i used the spring-security-oauth client library i found that it
>>> validated the resourceId against this aud claim.
>>>
>>> i thought it an unnecessary constraint at the time, but maybe it could be
>>> used to restrict access by tokens, which although may have the correct
>>> scope, have been issued to the incorrect or otherwise unknown client?
>>>
>>> Simon.
>>>
>>> On Wed, Aug 16, 2017 at 1:41 PM, Pablo Fernandez <
>> pablo.fernandez at cscs.ch>
>>> wrote:
>>>
>>>> Dear Keycloakers,
>>>>
>>>> I am (almost) new to Keycloak and having trouble, and I thought I should
>>>> ask you after exhausting other options, so here I am.
>>>>
>>>> What I would like to find is a way to confine certain web apps (with a
>>>> registered client in Keycloak) from accessing any other client that is
>>>> not supposed to. Specifically, I have an oidc client named 'keystone'
>>>> that handles all OpenStack authentication and another oidc client
>>>> 'simplewebapp' that is a webapp that I want to give access to 'keystone'
>>>> while NOT giving access to any of the other clients (e.g. account,
>>>> admin-cli, broker, etc.)
>>>>
>>>> Is there a way to do this?
>>>>
>>>> I thought about Scopes, but I see they are basically linked to Roles
>>>> that I think have nothing to do with what I am doing (I tried, though
>>>> creating new roles but it seems to me they don't prevent anything from
>>>> happening). If I have to use Scopes, then how? Is there a Role that I
>>>> can use to deny - or exclusively grant - access to another client? I
>>>> also tried changing the Default Policy in 'keystone' Authorization tab
>>>> to something like this (the opposite of what I wanted to do, to make it
>>>> fail and see if I can use this mechanism), without success:
>>>>
>>>> ---
>>>> // by default, grants any permission associated with this policy
>>>> //$evaluation.grant();
>>>> var context = $evaluation.getContext();
>>>> var contextAttributes = context.getAttributes();
>>>> if (contextAttributes.containsValue('kc.client.id', 'simplewebapp')) {
>>>>     $evaluation.deny();
>>>> }
>>>> $evaluation.grant();
>>>> ---
>>>>
>>>> I googled and browsed and tried many different setting combinations
>>>> without success, so I hope someone here could give me a hint.
>>>>
>>>> Thanks!
>>>> Pablo Fernandez
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> keycloak-user mailing list
>>>> keycloak-user at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/keycloak-user
>>>>
>>> _______________________________________________
>>> keycloak-user mailing list
>>> keycloak-user at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/keycloak-user
>>
>>
>> _______________________________________________
>> keycloak-user mailing list
>> keycloak-user at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/keycloak-user
>>
> _______________________________________________
> keycloak-user mailing list
> keycloak-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-user