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

Support more synced attributes for SCIM User Provisioning

XMLWordPrintable

    • 557
    • Hide

      5th November
      Thank you all for your feedback and to those who answered our survey.

      We have added a Location attribute to SCIM User Provisioning. To add Location, you will need to sync to the following attribute: 

      • Full Attribute: urn:scim:schemas:extension:atlassian-custom:1.0:Attributes:basedIn
        • Namespace: urn:scim:schemas:extension:atlassian-custom:1.0:Attributes
        • Attribute Name: basedIn

      We are continuing to work on adding the following attributes and will provide dates for them shortly:

      • Profile picture
      • Employee ID

      We will also be enabling automations for approval workflows for the Manager attribute.

      We understand the importance of this feature, and we will update this ticket with more information on specific dates as we have them.

      Our support documentation will be updated as new attributes are added:

       

      Thanks,
      Holly

      Show
      5th November Thank you all for your feedback and to those who answered our survey. We have added a Location attribute to SCIM User Provisioning. To add Location, you will need to sync to the following attribute:  Full Attribute : urn:scim:schemas:extension:atlassian-custom:1.0:Attributes:basedIn Namespace : urn:scim:schemas:extension:atlassian-custom:1.0:Attributes Attribute Name : basedIn We are continuing to work on adding the following attributes and will provide dates for them shortly: Profile picture Employee ID We will also be enabling automations for approval workflows for the Manager attribute. We understand the importance of this feature, and we will update this ticket with more information on specific dates as we have them. Our support documentation will be updated as new attributes are added: https://support.atlassian.com/provisioning-users/docs/understand-user-provisioning/ https://support.atlassian.com/provisioning-users/docs/sync-user-attributes-to-your-organization/   Thanks, Holly

    • 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.

      As per the user-provisioning documentation the feature currently supports the sync of:

      • Display name
      • Email address
      • Organization
      • Job title
      • Timezone
      • Department
      • Preferred language

      From provisioning perspective, it would be a good feature to allow custom attributes from third party IDPs to be synced into the Atlassian accounts. Sample use cases:

      • Profile photos
      • Location/Office/Based in
      • Manager (JSD approvals automatically set to the user's Manager)
      • Employee ID
      • Student ID's
      • Cost center

        1. image-2024-12-05-15-38-25-789.png
          image-2024-12-05-15-38-25-789.png
          71 kB
        2. image-2024-12-05-15-38-34-790.png
          image-2024-12-05-15-38-34-790.png
          100 kB
        3. Screen Shot 2022-09-30 at 16.16.55.png
          Screen Shot 2022-09-30 at 16.16.55.png
          1.44 MB

            [ACCESS-822] Support more synced attributes for SCIM User Provisioning

            Pinned comments

            Pinned by Cole Norman

            Holly Makris (Inactive) added a comment -

            For those of you asking about UPN sync for Entra, that is also in progress, scheduled to launch by the end of 2024. You can track progress here: https://jira.atlassian.com/browse/ACCESS-1560

            We have heard your feedback related to the Manager attribute. When Manager becomes available, you will also be able to use it for automating approvals, which is why it will take a bit longer to release than the other attributes.

            We will make sure the product teams are aware of the additional attributes and your feedback related to attribute automation.

            Thank you for your feedback!

            Holly Makris (Inactive) added a comment - For those of you asking about UPN sync for Entra, that is also in progress, scheduled to launch by the end of 2024. You can track progress here: https://jira.atlassian.com/browse/ACCESS-1560 We have heard your feedback related to the Manager attribute. When Manager becomes available, you will also be able to use it for automating approvals, which is why it will take a bit longer to release than the other attributes. We will make sure the product teams are aware of the additional attributes and your feedback related to attribute automation. Thank you for your feedback!

            Holly Makris (Inactive) added a comment -

            Thank your for your feedback on how to add the Location attribute. We have updated our documentation here: https://support.atlassian.com/provisioning-users/docs/sync-user-attributes-to-your-organization/

            Please do continue to post your questions and feedback, we are reviewing daily and will update the documentation to address any confusion.

            We will update this ticket with more information about the Employee ID and Profile picture attributes as well as Manager automations as soon as we have them. Please watch the Current Status section of this ticket for updates.

            Holly Makris (Inactive) added a comment - Thank your for your feedback on how to add the Location attribute. We have updated our documentation here: https://support.atlassian.com/provisioning-users/docs/sync-user-attributes-to-your-organization/ Please do continue to post your questions and feedback, we are reviewing daily and will update the documentation to address any confusion. We will update this ticket with more information about the Employee ID and Profile picture attributes as well as Manager automations as soon as we have them. Please watch the Current Status section of this ticket for updates.

            All comments

            Adrian Dubiel added a comment -

            Hi there!

            Is there any ETA when user photo attribute will be available for mapping?

            Thanks in the advance.

            Adrian Dubiel added a comment - Hi there! Is there any ETA when user photo attribute will be available for mapping? Thanks in the advance.

            Chris Riffey added a comment -

            Is the documentation going to be updated anytime soon? Photos from EntraID should be working now correct? How do we add them? 

            Chris Riffey added a comment - Is the documentation going to be updated anytime soon? Photos from EntraID should be working now correct? How do we add them? 

            Sami Shaik added a comment -

            This is much needed feature. 

            Sami Shaik added a comment - This is much needed feature. 

            Joe Johnson added a comment - - edited

            Hello all,

            Has any one had any issues with the EmployeeID attribute? We've added it in EntraID and for newly created/provisioned users it works fine, but for existing users the attribute is not being added. I'm adding screenshots here but I think they won't work in JAC:

            Joe Johnson added a comment - - edited Hello all, Has any one had any issues with the EmployeeID attribute? We've added it in EntraID and for newly created/provisioned users it works fine, but for existing users the attribute is not being added. I'm adding screenshots here but I think they won't work in JAC:

            Kim Walton added a comment -

            To add to the list, we would like to see a field added for Team(s) 

            Kim Walton added a comment - To add to the list, we would like to see a field added for Team(s) 

            Julien Béchade added a comment - - edited

            Hi e902c0832f88,

            When do you think you can update https://support.atlassian.com/provisioning-users/docs/sync-user-attributes-to-your-organization/ with how to use the new urn:ietf:params:scim:schemas:core:2.0:User:photos attribute?

            Maybe someone here has managed to use it already?
            Would appreciate if you could share your experience then.

            Cheers.

            Julien.

            Hello Julien,
            I am working with the engineer Krishna Turlapati Venkata to refine the documentation. the new "urn:ietf:params:scim:schemas:core:2.0:User:photos attribute" that we provided is the default attribute.

            Julien Béchade added a comment - - edited Hi e902c0832f88 , When do you think you can update https://support.atlassian.com/provisioning-users/docs/sync-user-attributes-to-your-organization/ with how to use the new urn:ietf:params:scim:schemas:core:2.0:User:photos attribute? Maybe someone here has managed to use it already? Would appreciate if you could share your experience then. Cheers. Julien. Hello Julien, I am working with the engineer Krishna Turlapati Venkata to refine the documentation. the new "urn:ietf:params:scim:schemas:core:2.0:User:photos attribute" that we provided is the default attribute.

            Julien Béchade added a comment -

            Ping e902c0832f88, see 9f2b0570cf8e's comment below 👇. We're all very anxious to get going with this 😄

            Julien Béchade added a comment - Ping e902c0832f88 , see 9f2b0570cf8e 's comment below 👇. We're all very anxious to get going with this 😄

            Samuel Segaud added a comment -

            Hi,

            The documentation was due to be updated on April 4 for the photo update.
            Unless I'm mistaken, this is not the case. Could you please let us know when this will be done?

            Samuel Segaud added a comment - Hi, The documentation was due to be updated on April 4 for the photo update. Unless I'm mistaken, this is not the case. Could you please let us know when this will be done?

            Constantin Tran added a comment -

            Constantin Tran added a comment -

            Matthias Fleschütz added a comment -

            7ce66bfac22e if that is the intention, the source attribute in Entra Id would be mailnickname.

            Entra's principle is UPN == email address, because you'll run into issues otherwise. Email is usually generated out of "alias", which is "mailnickname".

            The documentation of Atlassian should be updated / corrected regarding Entra.

            Matthias Fleschütz added a comment - 7ce66bfac22e if that is the intention, the source attribute in Entra Id would be mailnickname. Entra's principle is UPN == email address, because you'll run into issues otherwise. Email is usually generated out of "alias", which is "mailnickname". The documentation of Atlassian should be updated / corrected regarding Entra.

              e902c0832f88 Sudesh Peram
              rmacalinao Ramon M
              Votes:
              1048 Vote for this issue
              Watchers:
              622 Start watching this issue

                Created:
                Updated: