Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-17238

JLDAP provider should use a preferred name field if it exists

    XMLWordPrintable

    Details

    • Type: (Deprecated) Contributed Patch
    • Status: CLOSED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.8.0
    • Component/s: Providers
    • Labels:
      None
    • CLE Team Issue:
      Yes

      Description

      The JLDAP Provider has a set of fields that you can override in jldap-beans.xml. If you don't specify them, their values come from the defaults. However if you do override them and a value does not exist, no value is given at all.

      For instance in our LDAP setup we have the fields for first names:

      • givenName - full set of first name parts, ie Jonathon Edward where Jonathon is this person's firstname and Edward is his middle name. Cannot be changed.
      • ANUPreferredName - user specified, Jon, as that's what he prefers to be called.

      However to complicate matters, givenName is always set, ANUPreferredName not always, for instance with John Smith, his preferred name is John so it's no change.

      So we cannot just set ANUPreferredName as the mapping for a user's first name, otherwise some people will get nothing as their first name.

      There should be a preferredName field we can map that will be used preferentially, but will fall back to the givenName field if not set.

        Gliffy Diagrams

          Zeplin

            Attachments

              Activity

                People

                Assignee:
                steve.swinsburg Steve Swinsburg
                Reporter:
                steve.swinsburg Steve Swinsburg
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    Git Integration