Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-29272

Set User Display Name from multiple LDAP attributes

XMLWordPrintable

    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      Allow the User Display Name to be set from multiple LDAP attributes (e.g. title firstname middlename lastname) in the directory configuration. Currently only one attribute is supported.

            [CONFSERVER-29272] Set User Display Name from multiple LDAP attributes

            Martin Papproth added a comment -

            Hi Atlassian,
            you should reopen this suggestion and plan for an implementation.

            In multinational enterprises the LDAP is often a holy grail which cannot be modified. So having the chance to tweak the data while synchronizing it into the local Confluence user database would help a lot !

            Martin Papproth added a comment - Hi Atlassian, you should reopen this suggestion and plan for an implementation. In multinational enterprises the LDAP is often a holy grail which cannot be modified. So having the chance to tweak the data while synchronizing it into the local Confluence user database would help a lot !

            Nathan Given added a comment -

            I just tested this and it is working now (Confluence 5.6.1)... I don't see any exceptions in my catalina.out log nor in my atlassian-confluence.log .

            Here is what I configured my User Display Name Attribute to be:

            givenName sn

            I also tried setting my User Display Name Attribute to be:

            bogusField

            This also works... it seems that since the "bogusField" doesn't exist, the sync will automatically concatenate the field defined for "User First Name Attribute" and "User Last Name Attribute"

            Is this now a supported feature? (either one of the above options, are they supported?)

            Nathan Given added a comment - I just tested this and it is working now (Confluence 5.6.1)... I don't see any exceptions in my catalina.out log nor in my atlassian-confluence.log . Here is what I configured my User Display Name Attribute to be: givenName sn I also tried setting my User Display Name Attribute to be: bogusField This also works... it seems that since the "bogusField" doesn't exist, the sync will automatically concatenate the field defined for "User First Name Attribute" and "User Last Name Attribute" Is this now a supported feature? (either one of the above options, are they supported?)

            Frank added a comment -

            this should really be configurable without having to accept exceptions all over the log...

            Frank added a comment - this should really be configurable without having to accept exceptions all over the log...

            Chris Cope added a comment -

            Nevermind, it is broken. Anything that throws an exception, as in anything that's not a single field, defaults to "givenName sn".

            Chris Cope added a comment - Nevermind, it is broken. Anything that throws an exception, as in anything that's not a single field, defaults to "givenName sn".

            Chris Cope added a comment -

            This actually works for me in Confluence 5.1. For example:

            givenName sn

            returns "Chris Cope" for me.

            Chris Cope added a comment - This actually works for me in Confluence 5.1. For example: givenName sn returns "Chris Cope" for me.

            BillA added a comment -

            Thank you for raising this issue. While I can see how this feature would be useful, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Thanks again for your idea.

            BillA added a comment - Thank you for raising this issue. While I can see how this feature would be useful, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Thanks again for your idea.

              Unassigned Unassigned
              0c23b449d083 Nina Daalmann
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: