[keycloak-user] Principal name is showing different after switching to KC

Luis Rodríguez Fernández uo67113 at gmail.com
Mon May 7 07:50:09 EDT 2018


Hello Valsaraj,

I am not sure what your scenario is. Me, I am using a client java adapter
[1] for my tomcat applications. In my keycloak configuration file I have
something like:

<PrincipalNameMapping policy="FROM_ATTRIBUTE" attribute="
http://schemas.xmlsoap.org/claims/CommonName"/>

This tells keycloak which attribute use for the Principal.getName(). I
guess that for your scenario must be something equivalent.

Hope it helps,

Luis



[1]
https://www.keycloak.org/docs/latest/securing_apps/index.html#java-adapters-2






2018-05-07 9:19 GMT+02:00 valsaraj pv <valsarajpv at gmail.com>:

> Hi,
>
> UserPrincipal.getName showing cb3634be-e0e1-479e-aec9-0cb38c8a0468 like
> this after switching to Keyclock. LDAP uid was showing when we were using
> LDAP. After syncing users from LDAP to KC, when the application code checks
> user principal name, it shows this.
>
> Any thoughts?
>
> Thanks,
>
> Valsaraj Viswanathan
> _______________________________________________
> keycloak-user mailing list
> keycloak-user at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-user
>



-- 

"Ever tried. Ever failed. No matter. Try Again. Fail again. Fail better."

- Samuel Beckett


More information about the keycloak-user mailing list