RajiS.34215 (Customer) asked a question.
How to support SCIM multi-tenant feature through Okta
We are just getting started on supporting multi-tenancy through SCIM.
Our requirement is that:
Currently we support, a company XYZ which to provision users to their account in our SaaS application.
In the future, we want company XYZ to sync users to multiple accounts in our SaaS application from Okta directory.
- How can customer configure multi-tenancy in Okta?
- I read, Okta requires a base URL which can contain the tenant on which the request is made, for example "https://example.com/{tenant}/scim/v2/". Does this mean customer needs to clone configure multiple applications depending on the number of tenants they want to create?
- Can users overlap between these multiple tenants?
- Are there any restrictions on value of {tenant} in the url can be?
Hi @RajiS.34215 (Customer) , Thank you for reaching out to the Okta Community!
I think there might be an issue of nomenclature here. We typically refer to individual Okta orgs as "tenants", and for this we would recommend the Org2Org implementation. More details here:
https://help.okta.com/en-us/Content/Topics/Provisioning/org2org/org2org-main.htm
https://developer.okta.com/docs/concepts/multi-tenancy/
If you are looking to use just one Okta org to manage multiple SaaS apps, you will have to set up multiple app instances in you org for them.
I would imagine that users can overlap, and be directed to the proper resources as long as the trigger the appropriate endpoint.
As for restriction for the value of {tenant}, I was unable to find anything documented.
All this being said, my advice would be to reach out to the devforum.okta.com to take advantage of their expertise.
While we'll do our best to answer all of your questions here, this medium is more inclined towards Okta core products.
Hope my answer helps!
--------------------------------
The Okta Community Catalysts Program is now live. Collect online badges when you participate in the Okta Help Center Questions community. Learn more here.