Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-1229

Allow to sync and update the public name attribute via provisioning

XMLWordPrintable

    • 51

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      August 15, 2023 Update

      Hey all,

      The SCIM API accepts a 'nickName' attribute that will update an Atlassian account's Public Name. This mimics the user management API's update profile endpoint's functionality.

      Atlassian Cloud Apps in our supported identity providers do not send a 'nickName' attribute by default. However, these apps are flexible enough to map to the 'nickName' attribute. Contact your identity provider support team or Atlassian support for additional assistance.

      At the moment, only the Full name of the Atlassian Account can be updated via provisioning.

      Suggestion : Allow to sync and update the public name attribute via provisioning

            [ACCESS-1229] Allow to sync and update the public name attribute via provisioning

            Peter Cselotei - Lupus Consulting Zrt. added a comment -

            Displayname (Public name) is synced via mapping, but if Firstname and Lastname are synced too, they will overwrite it.

            I've created a workaround for that (we are using Microsoft Azure integration with Atlassian Access), please see this solution see on the Atlassian Community page.

            Best: Peter

            Peter Cselotei - Lupus Consulting Zrt. added a comment - Displayname (Public name) is synced via mapping, but if Firstname and Lastname are synced too, they will overwrite it. I've created a workaround for that (we are using Microsoft Azure integration with Atlassian Access), please see this solution see on the Atlassian Community page. Best: Peter

            Keima Ishihara added a comment -

            There is an issue with multiple hits for the same name when searching for a user to share an inquiry with.
            So when provisioning a user from Azure AD, we want to set their name and email address to the display name. However, we do not want to include the email address in the public name.

            Keima Ishihara added a comment - There is an issue with multiple hits for the same name when searching for a user to share an inquiry with. So when provisioning a user from Azure AD, we want to set their name and email address to the display name. However, we do not want to include the email address in the public name.

            Michael Henderson added a comment -

            It would be very nice and timesaving to have the Public Name as simply First Name Last name. In our situation we have email addresses with a period that is included between first name and last name. When a new user is created, and the email has this period, the Public Name inherits the period. We would like for this to be accounted for and removed if possible. The Service Desk has to login as that person and change the name for them. it is a step they would rather not have to do. Also, if not fixed, the users name apears as firstname.lastname in Jira issues.

            Michael Henderson added a comment - It would be very nice and timesaving to have the Public Name as simply First Name Last name. In our situation we have email addresses with a period that is included between first name and last name. When a new user is created, and the email has this period, the Public Name inherits the period. We would like for this to be accounted for and removed if possible. The Service Desk has to login as that person and change the name for them. it is a step they would rather not have to do. Also, if not fixed, the users name apears as firstname.lastname in Jira issues.

              maho Matthew Ho (Inactive)
              rmacalinao Ramon M
              Votes:
              24 Vote for this issue
              Watchers:
              34 Start watching this issue

                Created:
                Updated:
                Resolved: