JamalE.54083 (Customer) asked a question.
Currently we have one SPA using OKTA. We have a branding for it with subdomain app1.okta.com
so to access the OKTA admin console you use app1-admin.okta.com
We want to integrate a new SPA with complete different users base and different logo and branding.
What are the best practices here to have one OKTA org with 2 different branding?
Is it as simple as creating a new branding with new okta subdomain so that for users using the new app they get directed to app2.okta.com?
Does that mean we will have anew admin console app2-admin.okta.com?
How about authorization server? will that create a new default authorization server for that new sub domain?
I am trying to wrap my head around the concepts of org, tenant, identify provider and authorization server for each different application that require different branding? so I am looking for best practices
Thanks
Hi, @JamalE.54083 (Customer)
Thank you for posting on our Community page!
If you have a Custom Domain URL for your Okta Org, you can modify the Okta hosted widget. Each Org only has one hosted login widget. However you can modify its styling based on how it is accessed, one of those ways could be checking for a client_id in an /authorize URL. So it would be possible to present two different looking widgets for an Okta hosted login with a Custom Domain URL.
My advice would be to get in touch with your Account Executive and set up a meeting to see exactly what you need based on your configuration and requirements.
Thank you for reaching out to our Community and have a great day!
Subscribe Today: The Okta Community is on YouTube
_____________________________________________________________________________
Community members help others by clicking Like or Select as Best on responses. Try it today.
_____________________________________________________________________________