Re: [keycloak-user] How read added mapper attribute from ldap?

There are two mappings here Firstly you need an attribute mapper in user federation. This maps an LAP attribute to a Keycloak one. I don't think this works on existing users though. Try creating a new LDAP user and log in as that user to test this. Check the log. In my case it's at /var/log/wildfly/console.log but might have been moved there by one of our devs. Check USER_ATTRIBUTES table in the database. You should have a line for your new attribute for your new user. I know this doesn't work for multi-attribute values. eg we have an 'applications' attribute which users will have several entries. Secondly you need to map the user attribute you created above to the JWT token This is under your client application definition. You need a 'user attribute' not 'property' mapper to map the new keycloak user attribute to a value in the token(s) You also need to turn it on for either the id token or access token depending on where your client expects it. *Kevin Thorpe* CTO <https://www.p-i.net/> <https://twitter.com/@PI_150> www.p-i.net | @PI_150 <https://twitter.com/@PI_150> M: +44 (0)7425 160 368 | T: +44 (0)203 005 6750 | F: +44(0)207 730 2635 150 Buckingham Palace Road, London, SW1W 9TR, UK _____________________________ This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. *"SAVE PAPER - THINK BEFORE YOU PRINT!" * On 29 June 2015 at 13:02, Adam Daduev <daduev.ad(a)gmail.com&gt; wrote: