Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LDAP auth method Account Attribute Maps not populating #4422

Closed
bbarkhouse-hashicorp opened this issue Feb 16, 2024 · 1 comment
Closed

LDAP auth method Account Attribute Maps not populating #4422

bbarkhouse-hashicorp opened this issue Feb 16, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@bbarkhouse-hashicorp
Copy link

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:

  1. Create a new LDAP auth method
  2. 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.
  3. Save and enable the auth method.
  4. Open Boundary Desktop, select the scope and LDAP auth method just created
  5. Log in with valid users credentials from the target LDAP user dn
  6. Boundary Desktop successfully authenticates and takes me to the list of targets
  7. 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.
Screen Shot 2024-02-16 at 13 16 21 PM
Screen Shot 2024-02-16 at 13 19 15 PM

@bbarkhouse-hashicorp bbarkhouse-hashicorp added the bug Something isn't working label Feb 16, 2024
@moduli
Copy link
Collaborator

moduli commented Jun 3, 2024

Thanks for raising this issue. We've implemented a fix here and it should be included in the next non-patch release of Boundary.

@moduli moduli closed this as completed Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants