This guide teaches you how to integrate your federated SSO application with Okta. This guide assumes that you intend to make this app integration public by publishing it in the Okta Integration Network (OIN).
Create and test an SSO app integration for OIN submission.
Single Sign-On (SSO) is an authentication method that enables end users to sign in to multiple applications (apps) with one set of credentials. If you have customers that use Okta as an Identity Provider, you want to publish your SSO app integration to the OIN. By having your integration in the OIN catalog, your customers can easily configure SSO for your app. See Overview of Single Sign-On in the OIN for all the benefits of having your integration in the OIN catalog.
To create an SSO integration for the OIN, first sign up for a free Okta developer-edition org(opens new window). Next, select the type of SSO protocol that you want to implement. Okta supports two SSO standards for your integration:
OpenID Connect (OIDC) (preferred)
Security Assertion Markup Language (SAML)
Okta recommends using OIDC for new SSO integrations.
Note: Not all Okta SSO features are supported in the OIN. See OIN limitations.
This section assumes that you've built the SSO integration in your app.
After you've built your SSO integration, you can use the Application Integration Wizard (AIW) in the Admin Console to create your app integration instance. This instance provides you with client credentials or metadata for you to test your SSO flows.
Note: Creating your app integration instance doesn't automatically make it available in the OIN(opens new window). After you've tested your integration, you need to submit it to the OIN team for verification and publication.
Go to Applications > Applications in the Admin Console.
Click Create App Integration.
Specify your integration settings
This portion of the guide takes you through the steps for configuring your specific SSO integration using the Okta Admin Console.
After you create your integration instance in the Create your integration in Okta section, the main settings page appears for your new integration in the Admin Console. Specify General Settings and Sign On options, and assign the integration to users in your org. Click Edit if you need to change any of the options, and Save when you've made your changes.
Test your integration
This portion of the guide takes you through the steps required to test your integration.
First, you must assign your integration to one or more test users in your org:
Click the Assignments tab.
Click Assign and then select either Assign to People or Assign to Groups.
Enter the appropriate people or groups that you want to have Single Sign-On into your application, and then click Assign for each.
Verify the user-specific attributes for any people that you add, and then select Save and Go Back.
Test Single Sign-On
Sign out of your Okta org. Click Sign out in the upper-right corner of the Admin Console.
Sign in to the Okta End-User Dashboard as the regular user that was assigned the integration.
Note: If you sign in as a non-admin user to your Okta org from a browser, the End-User Dashboard appears. To access the End-User Dashboard from a mobile device, see Okta End-User-Dashboard(opens new window).
Click the Okta tile for the integration and confirm that the user is signed in to your app.