Bug #8339
closed
Transform white spaces to dots in LDAP login
Description
Since many LDAP sources in enterprises will be a Microsoft Active Directory where white spaces in login names are common it would be nice if when someone tries to login with such a login the white spaces would be transformed to dots so that a mapping for existing logins and creation of on-the-fly logins are possible.
Example: Login name "Foo Bar" would be transformed to "foo.bar"
Updated by Dominic Cleal over 9 years ago
- translation missing: en.field_release deleted (
27)
Updated by Andy Airey over 8 years ago
We have such an AD environment, it contains usernames (the 'sAMAccountName' LDAP Attribute) with spaces in it.
I am not able to create a user with a space in the name from within foreman.
I have tried replacing the whitespace with '%20' or a '.' to no avail.
When I try with a user which does not have a space in his sAMAccountName, it is working fine.
Updated by Marek Hulán over 7 years ago
- Status changed from New to Need more information
As mentioned in linked BZ, using userPrincipalName might be a better approach than allowing spaces in sAMAccountName. sAMAccountName is supposed to be used for backwards compatibility with legacy Microsoft systems. userPrincipalName contains user login name. Would that be a viable solution? We should probably fix it in our manual.
Updated by Bryan Kearney over 7 years ago
Marek, who do you need the info from?
-- bk
Updated by Marek Hulán over 7 years ago
Ideally from the reporter - Daniel Kröger. If this resolves his issue we can mark this as closed.
Updated by Marek Hulán over 7 years ago
- Status changed from Need more information to Feedback
Updated by Anonymous almost 7 years ago
- Status changed from Feedback to Resolved
no reaction, closing