Register your app

You can use either the Okta CLI or the Admin Console to register your app to your Okta org for user authentication. After your app is registered, your Okta org generates the issuer ID, client ID, and client secret for you to integrate into your app build.

The following instructions show you how to register a server-side web app to have an Okta-hosted sign-in page. For Admin Console instructions on how to register other supported app types and sign-in methods, see Create a new Okta app integration (opens new window).

Start from a sample app

You can review and build Okta's sample applications from GitHub to learn how the various languages or frameworks can be used for Okta authentication.

Find the sample applications that match your app's language or framework:

Framework Repository
ASP.Net (opens new window)
ASP.NET Core (opens new window)
ASP.Net Web Forms (opens new window)
Java Servlet (opens new window)
Java Spring (opens new window)
Angular (opens new window)
React (opens new window)
Vue (opens new window)
Golang (opens new window)
Node.js Express (opens new window)
Python Flask (opens new window)
PHP (opens new window)

For Okta-hosted sign-in implementations, explore the okta-hosted-login folder where several use case examples are provided.

Build the example app as-is, or use it as a template for modifying your own app. When you have an app running, you're ready to connect it to your Okta org.

Tell Okta about the app

Instructions for

Set values in environment variables or configuration file

After registering your app, you now have the specific values for client ID, client secret, and issuer ID required for your app integration. All the various example apps in Okta's GitHub provide ways of setting these values. Some example apps expect you to set environment variables, while others expect you to set parameters in a configuration file. Consult the README file for the example app you're using and set these three values.