-
Suggestion
-
Resolution: Duplicate
-
None
Problem Definition
As per the user-provisioning documentation the feature currently supports the sync of:
- Display name
- Email address
- Organization
- Job title
- Timezone
- Department
- Preferred language
But it's not possible to sync additional attributes (e.g. Based in, Employee ID).
Suggested Solution
Add support for additional attributes from the identity provider that may be added in the future.
- blocks
-
ACCESS-653 Migrating from Atlassian Server products where SCIM was enabled to Atlassian Cloud and then using Atlassian Access SCIM causes users to be given GUID usernames
-
- Closed
-
- duplicates
-
- In Progress
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
- is related to
-
- Closed
[ACCESS-657] Support more attributes for user-provisioning
Hi everyone,
We noticed that this improvement wasn't delivered for a while and I am happy to share with you one more solution that may help you to achieve this goal (or complementary need of your company) - MindPro Sync, a new Marketplace app, where you can integrate OKTA, Azure AD, or OneLogin with Jira and JSM.
With this integration, you can:
- Connect JIRA and JSM with your favorite Identity Provider (OKTA, Azure, or OneLogin);
- Select and map user attributes to be displayed in Jira issues or JSM requests (and portal), making ticket resolution faster;
- Use user attributes information from read-only custom fields to create JQL queries, filters, dashboards or to connect with other apps;
- Choose to display data for the issue Reporter or Assignee;
- Show user reporting hierarchy in Issues and JSM requests to facilitate escalation and approvals;
- Automatically assign approvers based on user hierarchy.
Available on Atlassian Marketplace for 30-days free: MindPro Sync
Check the app documentation: https://mindpro.atlassian.net/wiki/spaces/MAP/pages/1700298761/Mindpro+Sync
Learn more at: mindproapps.com
Eduardo,
MindPro - Atlassian Marketplace Partner
Thanks everyone for watching and commenting on this ticket. As part of an initiative to better consolidate customer feedback, we are closing this ticket as a duplicate. Please vote, watch and comment on ACCESS-822 going forward.
Phone number also is required for some of our customers.
My 2 cents here:
- in an ideal world, we should allow to map any attribute that is present in the active directory, in this way we only synchronize what is strictly required.
- Also think different: instead of synchronizing, it would be perfect, if possible, that Access queries the AD tenant to retrieve the information on the fly, in this way Atlassian does not need to store this data, optimizing the infrastructure and reducing the synchronization activity. I am sure that while we need to retrieve the data profile - this activity is not constantly done to justify the whole dataset to be stored at Atlassian's infrastructure.
- This could be an Atlassian Access Premium option only for those customer that need the feature.
Best regards
Claudio Ombrella
co-CEO Digilac Sàrl - Atlassian Silver Solution Partner
www.digilac.ch
Another vote for manager and office location (among other attributes).
These attributes are defined in RFC7643 and should be supported.
| SCIM Attribute | Okta User Attribute |
|---|---|
| externalId | login |
| profileUrl | profileUrl |
| userType | userType |
| locale | locale |
| addresses[type eq "work"].formatted | postalAddress |
| addresses[type eq "work"].streetAddress | streetAddress |
| addresses[type eq "work"].locality | city |
| addresses[type eq "work"].region | state |
| addresses[type eq "work"].postalCode | zipCode |
| addresses[type eq "work"].country | countryCode |
| urn:ietf:params:scim:schemas:extension:enterprise:2.0:User.employeeNumber | employeeNumber |
| urn:ietf:params:scim:schemas:extension:enterprise:2.0:User.costCenter | costCenter |
| urn:ietf:params:scim:schemas:extension:enterprise:2.0:User.division | division |
| urn:ietf:params:scim:schemas:extension:enterprise:2.0:User.manager.value | managerId |
- External ID should solve
ACCESS-653. - Locality should solve
ACCESS-766. - Manager should solve ACCESS-822.
There are also complex object attributes:
- ims
- photos (would solve
ACCESS-785) - entitlements
- x509certificates
- roles
Please make this happen, the manager attribute is especially important for ITSM deployments and approval automations.
Equally, we urgently need Office Location available in Jira Cloud.
This was available in Jira on Prem and it’s a blocker for us not having this information in above version.
Please advise?
Many thanks.
Could you provide an update? We would like to sync more attributes to provide users with a way to understand the Org Chart. Here are a few more fields that would be a priority:
Office Location
Division
Manager
Please add "Based in" for mapping with Azure AD / SCIM provisioning.