7:43 a.m.
Dear All
We have configured the AD Authentication in Keycloak using the User Federation. Currently
we are configured the Username LDAP Attribute as "cn", but in our of the
application, we need to send the sAMAccountName as the login parameter
So kindly support in configuring the sAMAccountName as Protocol Mapper.
[All]
Above email is subject to 'Disclaimer' as per <a
href="http://tafe.co.in/email-disclaimer.htm">http://tafe.co.in/email-disclaimer.htm</a>
10:31 a.m.
If I understand your usecase, you need 2 things:
1) Configure LDAP User Attribute mapper and map LDAP Attribute
'sAMAccountName' to any attribute of user. After doing this, you should
be able to see the the sAMAccountName-mapped attribute in the tab
"Atrributes" of particular user in Keycloak admin console.
2) Create protocolMapper for your client application and map the
attribute from (1) to the claim of the token with User Attribute
protocol mapper. Then in your application, you should see the
corresponding claim in the access token.
Marek
On 29/01/18 14:43, trmadhu(a)tafe.com wrote:
Dear All
We have configured the AD Authentication in Keycloak using the User Federation. Currently
we are configured the Username LDAP Attribute as "cn", but in our of the
application, we need to send the sAMAccountName as the login parameter
So kindly support in configuring the sAMAccountName as Protocol Mapper.
[All]
Above email is subject to 'Disclaimer' as per <a
href="http://tafe.co.in/email-disclaimer.htm">http://tafe.co.in/email-disclaimer.htm</a>
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user
2537
days inactive
2537
days old
1 comments
2 participants
participants (2)
-
Marek Posolda -
trmadhu＠tafe.com