Using Okta as user data store for public web application? Skip to main content
https://support.okta.com/help/answers?id=9062a000000bm6vqaa&refurl=http%3a%2f%2fsupport.okta.com%2fhelp%2fanswers
How satisfied are you with the Okta Help Center?
Thank you for your feedback!
How satisfied are you with the Okta Help Center?
1
2
3
4
5
Very Dissatisfied
Very satisfied
Enter content less than 200 characters.
Ask Search:
Samuel NSamuel N 

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 KirkThomas 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.