I ran into the same issue with the realm roles. The problem is that the documentation for methods such as getUser should make it clear that the UserRepresentation returns only a subset of the fields. The same goes for creating a user - certain fields in the UserRepresentation such as roles, password are ignored. 

2016-08-09 15:04 GMT+02:00 Marek Posolda <mposolda@redhat.com>:
On 09/08/16 11:48, NEMECKAY Marek wrote:
Dear all,
 
We are facing a problem with retrieving the client roles from Keycloak. In our implementation we are using the following API to find a retrieve user data via username:
It seems that you need different admin REST endpoint to get the client role mappings of user. It's this one : 
GET /admin/realms/{realm}/users/{id}/role-mappings/clients/{client}

Marek
 
In the retrieved UserRepresentation object instance the property clientRoles is always null. We are using Keycloak 1.9.8 connected to a LDAP server for user federation. We are connecting a receiving the access token with a admin-user of the corresponding realm. This works just fine. We are also receiving user data like name, e-mail etc., but the client roles are always null. The mappers to sync roles between Keycloak and LDAP are also defined and working.
 
Is there anything else we have overlooked or we should check?
 
Thanks and BR,
Marek
 
 

_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user


_______________________________________________
keycloak-user mailing list
keycloak-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user