LDAP: Synthesize a displayname from surname, givenname #151
Labels
Comments
|
I just filed #800 which is related and/or a duplicate. Does your schema have |
stevendanna
added a commit
that referenced
this issue
Nov 5, 2016
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
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
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
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
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
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
As a customer, I would like the chef server LDAP module to create a
displaynamefield by copying thenameattribute, or concatenating thegivennameandsurnameattributes together with a space.For example, my LDAP record might have this, but no
displayname. Name is a good substitute in this case.Alternatively, my LDAP record might have this and no
displaynameThe Chef server's ldap module should just concatenate those values with a space into
displaynameand create the chef server user record using that.If neither of these avenues are taken by the chef server against an LDAP server lacking
displaynameattributes for users, their name shows up as"unknown"in the Manage interface.The text was updated successfully, but these errors were encountered: