<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
0D51Y00009Y0ElXSAVOkta Classic EngineIntegrationsAnswered2020-10-05T08:33:13.000Z2020-09-26T15:55:48.000Z2020-10-05T08:33:13.000Z

vaibhavg.25666 (Customer) asked a question.

Self hosted application,different clients with sub-domains,single code base,different databases,clients with OKTA orgs.How to implement OKTA SSO?
  • The application is hosted on our server.
  • Our clients have been provided with different subdomains to use it.
  • Each subdomain has a different database. We have another common database that has information regarding all the clients as to what database to connect and which URL points to which client etc.
  • All our clients have an Okta account and have their Orgs setup.
  • I want to implement Okta SSO for all the clients, wherein users of each client click on a button in our application and are redirected to their companies Okta Orgs and are authenticated and redirected back to our application

 

How do I do it without using OWIN middleware or any middleware for that matter?

OR

If I have to use OWIN middleware then what code goes into it?

I have followed the normal flow which was available on OKTA and other places on the internet.

 

The problem with using middleware is as follows:

OWIN Middleware for Okta mandatorily requires clientId, redirectUrl, etc to be passed as openIdConnect options.

I fetch these from the database but since it runs at application startup and I am not able to pass the values (clientId, redirectUrl, etc) dynamically.

 

This is turning out to be a bottleneck for us and we are not able to move forward from here.

Any help will be appreciated.

 

We are using C* and ASP.NET and .NET Framework 4.7


This question is closed.
Loading
Self hosted application,different clients with sub-domains,single code base,different databases,clients with OKTA orgs.How to implement OKTA SSO?