Comments
-
Hi Negin, I think I found your case with our Support team (PCS-441552) and the affected user. Looking at the SCIM DB, it never got the command for updating the group memberships, we only got the Deactivation command. So in order for it to update on Atlassian, Okta must first push it to the SCIM DB. This may happen if you…
-
Hello @Negin Nafari Thank you for your comment! The Directory ID for the userbase is not the same as the SCIM Directory ID, those are two separate userbases (perhaps this isn't clear on this article). The endpoint you are sharing, is one for User Provisioning and uses a SCIM Directory. The endpoint mentioned in my update…
-
@Pascal BELLEBOUCHE, Are you referring to the Directory ID Endpoint? Can you share the error you are seeing?
-
👋 Update 23 May 2025 The steps mentioned in this article are no longer necessary to retrieve the Directory ID. We have now made available an API endpoint that queries the Directory ID more easily. You can find the endpoint here. The only information required are the Org ID and the API Key. Both can be extracted from…
-
Hello @Cristian Iorio Sorry for the late reply on this. The Feature Request you've mentioned is about Azure AD/Entra ID OSync. Basically there are two ways of provisioning to Atlassian using Azure AD: * Through SCIM, which requires a manual configuration on Atlassian. * Through OSync, which is a one-click setup where you…
-
Hello @Krystien Hart, Thank you for your effort. I'll gladly help with making sure this is visible on other KB articles! The only documentation I know of which refers to the directoryId is on our REST API docs. Do you have any particular articles where you've seen the directoryId mentioned?
-
Hello everyone, If you have issues with running the endpoint, it may be because of an incorrect Directory ID (which is not the SCIM directory ID - but rather the userbase directory). I've written this post to help out with retrieving the Directory…
