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.

Sign up for GitHub

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

Jump to bottom

Allow setting LDAP "displayName" attribute in Chef Server #800

Closed
docwhat opened this issue Apr 7, 2016 · 0 comments · Fixed by #1001
Closed

Allow setting LDAP "displayName" attribute in Chef Server #800

docwhat opened this issue Apr 7, 2016 · 0 comments · Fixed by #1001
Labels
Component: ldap

Comments

@docwhat
Copy link

docwhat commented Apr 7, 2016

In our LDAP schema, the user's "name" isn't displayName (like in Active Directory) but rather cn.

When using the Management console, it shows the user as "unknown" in the upper-right.

I think this is code in question:

chef-server/src/oc_erchef/apps/oc_chef_wm/src/oc_chef_wm_authn_ldap.erl

Line 200 in bb28b48

LookupFields = [{"displayname", <<"display_name">>},

In my experience, displayName is Active Directory only and everyone else uses cn (common name).
@docwhat docwhat mentioned this issue Apr 7, 2016
Closed
@marcparadise marcparadise mentioned this issue Nov 4, 2016
Closed
stevendanna added a commit that referenced this issue Nov 5, 2016
@stevendanna
[ldap] Allow user customization of field mapping
925cbaa 
Attributes from a user's LDAP record are used during account-linking to
populate the erchef user record when it is created. Previously, the
mapping between LDAP attributes and chef user attributes were fixed.
Now, they are configurable.

For example, if the user's LDAP record stores their email address in a
field named 'address' instead of 'mail', then you could set the
following in private-chef.rb:

    ldap['email_attribute'] = "address"

Fixes #151
Fixes #800
Fixes #104
Partially addresses #675

Issue #800 was also addressed in #863 which allowed common_name to
service as a fallback for display name. The fallback is still in place
but now any field can be used for the display_name.

Issue #675 is an issue which our unicode handling. The unicode handling
is still broken; however, this would allow users to use a different
field that might not contain multi-byte characters.

Signed-off-by: Steven Danna <[email protected]>
@stevendanna stevendanna mentioned this issue Nov 5, 2016
Merged
stevendanna added a commit that referenced this issue Dec 7, 2016
@stevendanna
[ldap] Allow user customization of field mapping
b6b952e 
Attributes from a user's LDAP record are used during account-linking to
populate the erchef user record when it is created. Previously, the
mapping between LDAP attributes and chef user attributes were fixed.
Now, they are configurable.

For example, if the user's LDAP record stores their email address in a
field named 'address' instead of 'mail', then you could set the
following in private-chef.rb:

    ldap['email_attribute'] = "address"

Fixes #151
Fixes #800
Fixes #104
Partially addresses #675

Issue #800 was also addressed in #863 which allowed common_name to
service as a fallback for display name. The fallback is still in place
but now any field can be used for the display_name.

Issue #675 is an issue which our unicode handling. The unicode handling
is still broken; however, this would allow users to use a different
field that might not contain multi-byte characters.

Signed-off-by: Steven Danna <[email protected]>
stevendanna added a commit that referenced this issue Dec 7, 2016
@stevendanna
[ldap] Allow user customization of field mapping
1bcfeec 
Attributes from a user's LDAP record are used during account-linking to
populate the erchef user record when it is created. Previously, the
mapping between LDAP attributes and chef user attributes were fixed.
Now, they are configurable.

For example, if the user's LDAP record stores their email address in a
field named 'address' instead of 'mail', then you could set the
following in private-chef.rb:

    ldap['email_attribute'] = "address"

Fixes #151
Fixes #800
Fixes #104
Partially addresses #675

Issue #800 was also addressed in #863 which allowed common_name to
service as a fallback for display name. The fallback is still in place
but now any field can be used for the display_name.

Issue #675 is an issue which our unicode handling. The unicode handling
is still broken; however, this would allow users to use a different
field that might not contain multi-byte characters.

Signed-off-by: Steven Danna <[email protected]>
stevendanna added a commit that referenced this issue Jan 23, 2017
@stevendanna
[ldap] Allow user customization of field mapping
4901134 
Attributes from a user's LDAP record are used during account-linking to
populate the erchef user record when it is created. Previously, the
mapping between LDAP attributes and chef user attributes were fixed.
Now, they are configurable.

For example, if the user's LDAP record stores their email address in a
field named 'address' instead of 'mail', then you could set the
following in private-chef.rb:

    ldap['email_attribute'] = "address"

Fixes #151
Fixes #800
Fixes #104
Partially addresses #675

Issue #800 was also addressed in #863 which allowed common_name to
service as a fallback for display name. The fallback is still in place
but now any field can be used for the display_name.

Issue #675 is an issue which our unicode handling. The unicode handling
is still broken; however, this would allow users to use a different
field that might not contain multi-byte characters.

Signed-off-by: Steven Danna <[email protected]>
stevendanna added a commit that referenced this issue Jan 23, 2017
@stevendanna
[ldap] Allow user customization of field mapping
3277111 
Attributes from a user's LDAP record are used during account-linking to
populate the erchef user record when it is created. Previously, the
mapping between LDAP attributes and chef user attributes were fixed.
Now, they are configurable.

For example, if the user's LDAP record stores their email address in a
field named 'address' instead of 'mail', then you could set the
following in private-chef.rb:

    ldap['email_attribute'] = "address"

Fixes #151
Fixes #800
Fixes #104
Partially addresses #675

Issue #800 was also addressed in #863 which allowed common_name to
service as a fallback for display name. The fallback is still in place
but now any field can be used for the display_name.

Issue #675 is an issue which our unicode handling. The unicode handling
is still broken; however, this would allow users to use a different
field that might not contain multi-byte characters.

Signed-off-by: Steven Danna <[email protected]>
stevendanna added a commit that referenced this issue Apr 3, 2017
@stevendanna
[ldap] Allow user customization of field mapping
83f6c1e 
Attributes from a user's LDAP record are used during account-linking to
populate the erchef user record when it is created. Previously, the
mapping between LDAP attributes and chef user attributes were fixed.
Now, they are configurable.

For example, if the user's LDAP record stores their email address in a
field named 'address' instead of 'mail', then you could set the
following in private-chef.rb:

    ldap['email_attribute'] = "address"

Fixes #151
Fixes #800
Fixes #104
Partially addresses #675

Issue #800 was also addressed in #863 which allowed common_name to
service as a fallback for display name. The fallback is still in place
but now any field can be used for the display_name.

Issue #675 is an issue which our unicode handling. The unicode handling
is still broken; however, this would allow users to use a different
field that might not contain multi-byte characters.

Signed-off-by: Steven Danna <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Component: ldap
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[ldap] Allow user customization of field mapping chef/chef-server
2 participants
@docwhat @stevendanna