Single sign-on · Setup guides
Okta
Set up a SAML 2.0 application in Okta and connect it to OrbitID. You need admin access to the Okta org.
Step 1: Create application
From your Okta account, click Applications from the left navigation menu.
If your application is already created, choose it from the list and move to the next step.
If you haven't created a SAML application, click the Create App Integration button to create a new application.

Choose SAML 2.0 from the next screen and click Next.

Give your application an App Name and click Next.

Step 2: Configure application
Enter the following values in the SAML Settings section on the next screen:
- Single sign on URL
- https://app.orbitid.com/api/oauth/saml
- The ACS URL shown in your OrbitID Configuration page. Sandbox uses https://app.orbitid.com/api/oauth/sandbox/saml.
- Audience URI (SP Entity ID)
- https://saml.orbitid.com
- The SP Entity ID shown in your OrbitID Configuration page. Sandbox uses https://saml.orbitid.com/sandbox.
Select EmailAddress from the Name ID format dropdown.

Step 3: Attribute mapping
Under the Attribute Statements section, you have to configure the following attributes:
| Name | Value |
|---|---|
| id | user.id |
| user.email | |
| firstName | user.firstName |
| lastName | user.lastName |

On the next screen select I'm an Okta customer adding an internal app and click Finish.

Step 4: Copy the IdP metadata
From your application, click the Sign On tab and go to the section SAML Signing Certificates.
Click the Actions dropdown for the correct certificate and click View IdP metadata.
A separate window will open with the metadata XML file. Copy the URL of that window (the metadata URL) or the XML itself to your clipboard.

Finish in OrbitID
Finish in OrbitID: paste the IdP metadata URL or XML into the connection form (or the Admin Portal link). In the dashboard, open the environment, go to Connections, click New connection, choose SAML and paste the metadata URL or the XML you downloaded. If your customer's admin is following an Admin Portal link, they paste it into the final step of the portal instead.
You can also create the connection with the API: POST /api/v1/sso as described in the quickstart.

