<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D51Y00008Qo4GrSAJOkta Classic EngineSingle Sign-OnAnswered2024-03-25T17:10:42.000Z2020-05-12T18:04:52.000Z2020-05-12T18:12:08.000Z

v2nt4 (v2nt4) asked a question.

Multi-tenant OpenID Connect application

We're a SaaS startup and we want to provide our clients (organizations) an option to use SSO.

 

Each of our clients has a separate Okta instance (they’re completely independent companies/organizations).

 

So we want to provide an SSO option this way, that all of their users can use a single published application in the app market.

 

We found a way that our clients can configure a Custom Connector in order to use SSO, they should provide a name and logo for it, login endpoints. They should copy-paste Client ID/Secret and etc.

 

 

This experience doesn’t look right. 

 

We want our application to be published and to have a logo/name pre-defined. So our customers can easily find it in the market without creating it.

 

We want to use the OpenID Connect protocol. Is it possible to publish this kind of application and will it work this way? That several organizations can just add it and start to use it to log in to our SaaS.

 

Mb it's possible with SAML?

 

 


This question is closed.
Loading
Multi-tenant OpenID Connect application