Hi,
Hope you are doing good
We implemented SSO around a year ago, basically when a user leaves company he/she will be removed from the SSO which will subsequently remove the user from the Atlassian.
Looks the intended functionality is not working, below are few examples:
Since this is marked for Cloud, SSO (via Atlassian Access, as there is no other way) doesn't remove users, only adds them.
To make removal (or to be precise deactivation) automatic you need to implement User Provisioning functionality of Atlassian Access. This depends on whether your Identity Provider supports SCIM protocol.
I am not sure what is the role of "Apollo" in the question, and simple googling doesn't really reveal it, but some resources do mention SAML SSO between Apollo GraphOS and AzureAD or OKTA. Both of these IdPs do support SCIM, so User Provisioning and De-provisioning can be in fact configured.
Specific Emails here won't help, this is the community site. Nobody here has access to your instance, or knows anything about your settings.
Your problem likely means you need to be using Atlassian Access (the Atlassian SAML SSO product) to automatically disable access to Atlassian products when they leave your org.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.