We have a case where existing users keep inviting new users from the company to the application. Now even though we have SCIM enabled the users register via the manual method and are out of sync with the IdP SCIM and cannot be managed by SCIM.
Now I know, Okta has an import function to resolve this but thats not something I am given access to. So wondering if there is another way to enable on-going sync with IdP so that any new manually added user becomes managed by SCIM at a later point?
I understand the requirements: Yes, the user must exist in our IdP group for authentication/SSO but might not have been assigned the app for SCIM group provisioning. Does that make sense? Or am I doing something wrong?
Agreed. If the user has already been invited manually and you assign a user with the same email address in Okta, then we will match it to the existing account. The profile details from Okta will become the source of truth and the user will be fully managed in Okta like any other IdP-managed user.
On the end user's side, they won't notice a thing unless they had manually set profile details (like job title) already. In that case they would get overwritten by the values from Okta.
Did you know Atlassian Access offers more than SAML single sign-on for Atlassian cloud products, like Jira and Confluence? Whether you're just starting to plan for your organization or in the pr...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events