<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
0D50Z00008G7VMESA3Okta Classic EngineAdministrationAnswered2020-09-08T20:50:21.000Z2016-10-24T16:06:03.000Z2020-09-08T20:50:21.000Z
Using Okta as user data store for public web application?
We're looking at using Okta as the user data store and auth service behind a public website. We'll manage users through the API and user info will only be stored in our one Okta instance. We may use single sign on with other apps we create in the future, but for now Okta is only authenticating with our one app.

 

We're not looking to have organizations with Okta auth with their Okta instances against our app. Every user will have a user record in our Okta instance.

 

Is this even a common use case for Okta? I haven't found any documentation or information the helps with this type of setup. Any pointers?

 

Thanks,

 

Sam

 


  • Thomas Kirk (Okta, Inc.)

    This is a pretty common scenario. When it comes to using Okta for Auth and user directory you really have a handfull of options.

     

    You can SSO enable your application and use standard SSO technologies such as SAML, WS-Fed and OIDC. Another option is to do a pure API based approach.

     

    I would say the use cases you are looking to support will determine the best approach to your application.
    Expand Post
  • HisashiY.98105 (Customer)

    I just wanted to understand what kind of database solution(i.g. RDBMS, NoSQL) okta's user data store is using.

This question is closed.
Loading
Using Okta as user data store for public web application?