You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When account attribute maps are set within a LDAP auth method, the From Attributes are not populating the To Attributes in the individual user accounts.
To Reproduce
Steps to reproduce the behavior:
Create a new LDAP auth method
Configure all settings and set the account attribute map based on the user attributes in your directory. In my case I mapped cn to fullName and mail to email.
Save and enable the auth method.
Open Boundary Desktop, select the scope and LDAP auth method just created
Log in with valid users credentials from the target LDAP user dn
Boundary Desktop successfully authenticates and takes me to the list of targets
Go back to the admin UI and you will see the new account associated with the LDAP auth method. However only the id, DN and groups attributes are populated. Full Name and Email are blank even though they were mapped in the auth method config.
Expected behavior
When account attribute maps are set within a LDAP auth method, I expect the attributes to populate the user account with values. For example, if cn is mapped to fullName, when the LDAP user authenticate to Boundary, the user account gets created in Boundary but the Full Name field is blank. I expected the cn value to be populated.
The text was updated successfully, but these errors were encountered:
Describe the bug
When account attribute maps are set within a LDAP auth method, the From Attributes are not populating the To Attributes in the individual user accounts.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
When account attribute maps are set within a LDAP auth method, I expect the attributes to populate the user account with values. For example, if cn is mapped to fullName, when the LDAP user authenticate to Boundary, the user account gets created in Boundary but the Full Name field is blank. I expected the cn value to be populated.
The text was updated successfully, but these errors were encountered: