You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
We're tracking customer demand for nested groups support here: https://jira.atlassian.com/browse/ACCESS-654
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This seems confusing, I have a group setup to sync in Atlassian cloud, and the group does sync to the cloud, but the users in the group are not added to the access policy.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.