Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,458,230
Community Members
 
Community Events
176
Community Groups

Does Atlassian Access support nested groups?

I'm trying to write a script that will sync groups from our LDAP system to Atlassian Access because the Google connector only syncs users. The script uses the documented APIs.

According to the schema, it *looks* like the reference can point at users and groups. Unfortunately, the documentation only references users:

The User provisioning REST API REST API (atlassian.com)

If I try to patch the membership of a group with the id of a group, I get this error:

{"schemas":["urn:ietf:params:scim:api:messages:2.0:Error"],"status":"400","scimType":"invalidValue","detail":"Resource [USER] Missing user: REDACTED"}

The payload only seems to require "value" and "display". I've tried explicitly specifying $ref so that it is clear that a group is being referenced but I'm still getting the same error.

 

1 answer

1 accepted

0 votes
Answer accepted

Hi @Philip Colmer 

Welcome to community! Atlassian access or rather Atlassian Cloud doesn't have group nesting for users. the failure for 400 error is because payload is invalid. Please can you share the payload you're using.

OK - if there isn't support for group nesting, I'll just sync flattened lists of members instead.

Thanks for the confirmation.

Dave Meyer Atlassian Team Nov 08, 2020

Just for context, the primary reason that Atlassian does not support nested groups for user provisioning is that this feature is not supported by major cloud identity providers like Microsoft Azure AD and Okta, which account for the vast majority of our user provisioning API usage. 

https://help.okta.com/en/prod/Content/Topics/users-groups-profiles/usgp-groups-main.htm

https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/how-provisioning-works#scoping

We're tracking customer demand for nested groups support here: https://jira.atlassian.com/browse/ACCESS-654

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events