---
title: Okta SSO (OIDC)
description: "##### **Supported Features** SecurEnds application supports the following OIDC feature: - Service Provider (SP)-Initiated Authentication (SSO) Flow ##### **Step 1: Add SecurEnds Application in Okta dashboard** - Within the Okta Admin dashboard select the **Applications** link in the header of…"
url: "https://se-stage.securends.com/documentation/okta-sso/"
updated: "2022-01-26"
category: "Credential Entitlement Management (CEM) / Single Sign-On (SSO)"
---

# Okta SSO (OIDC)

##### **Supported Features**

SecurEnds application supports the following OIDC feature:

- Service Provider (SP)-Initiated Authentication (SSO) Flow

##### **Step 1: Add SecurEnds Application in Okta dashboard**

- Within the Okta Admin dashboard select the **Applications** link in the header of the page

![](https://www.securends.com/wp-content/uploads/2020/12/2020-12-18_14-48-14-1024x601.png)

- Select the **Add Application** button on the **Application** screen

![](https://www.securends.com/wp-content/uploads/2020/12/2020-12-18_14-49-49-1024x560.png)

![](https://www.securends.com/wp-content/uploads/2020/12/2020-12-18_14-50-00-1-1024x539.png)

- Search for “SecurEnds” application and select the SecurEnds application from the results shown

![](https://www.securends.com/wp-content/uploads/2020/12/2020-12-18_14-52-21-1024x461.png)

- Select the **Add** button on the **SecurEnds** screen

![](https://www.securends.com/wp-content/uploads/2020/12/2020-12-18_15-38-04-1024x525.png)

- Provide **Application** **label** and **Sub** **Domain** details and select the **Done** button
- Example Application Label
  - SecurEnds
- Example Sub Domain
  - If the URL is "https://test.securends.com/" then the Sub Domain will be "test", the first part of the URL prior to ".securends.com"

![](https://www.securends.com/wp-content/uploads/2020/12/2020-12-18_14-54-35-1024x574.png)

- You will then be redirected to view the SecurEnds application details

![](https://www.securends.com/wp-content/uploads/2020/12/2020-12-18_14-56-31-1024x645.png)

- Select the **Sign** **On** tab, copy the **Client** **ID** and **Client** **secret** values. These values will need to be provided to your SecurEnds Implementation Consultant to be configured within your organizations SecurEnds instance
  - The following information will need to be provided to enable Okta SSO
    - Client ID
    - Issuer
    - Client Secret

![](https://www.securends.com/wp-content/uploads/2020/12/2020-12-18_14-56-02-1024x639.png)

- Once the application is created, go to General Tab
- Navigate to the App Embedded Link Section and copy the URL up until "okta.com"
  - This will be the **Issuer** URL required to enable your organization's SSO in SecurEnds
    - Example Issuer URL: **https://dev-577759.okta.com**

![](https://www.securends.com/wp-content/uploads/2020/12/2020-12-18_14-57-46-1024x526.png)

- Please provide the following information to your SecurEnds Implementation Consultant to be configured within your organizations SecurEnds Instance
  1. **Client ID**
  2. **Client Secret**
  3. **Issuer**

##### **Test Your Integration**

##### Step 2: Assign Users

First you must assign your integration to one or more test users in your org:

1. Select the **Assignments** tab
2. Select **Assign** and then select either **Assign** **to** **People** or **Assign** **to** **Groups**
3. Enter the appropriate users or groups that you wish to enable Single Sign-On into your application, and then select **Assign** for each
4. For any users that you added, verify the user-specific attributes, and then select **Save and Go Back**
5. Select **Done**

##### **Test Single Sign-On**

1. Sign out of your administrator account within your development org by selecting **Sign** **out** in the upper-right corner of the Admin Console
2. Sign in to the Okta End-User Dashboard as the normal user who was assigned the SecurEnds integration
3. In your dashboard, select the Okta tile for the integration and confirm that the user is signed into SecurEnds application

##### **Notes**

Users can access SecurEnds application using OIDC features in the following ways:

1. Customer can login to their okta org url
   - After authentication, customer can click on the SecurEnds App available in the dashboard and will be redirected to the SecurEnds application
2. Access SecurEnds instance url directly
   - Customer will be redirected to their okta org for authentication and after authentication customer will be redirected back to SecurEnds application

##### **Troubleshooting and Tips**

If you run into issues with your sign-in process, you can try the following to troubleshoot the issues:

1. In the Admin Console of your Okta development org, navigate to Reports > System Log and examine any failure messages reported
2. Open the developer console of your web browser and examine any status messages related to your authentication request. The console errors have status codes in the 4XX range. Investigate and resolve any error messages generated by your sign-on request
3. Please reach out to the SecurEnds Implementation Consultant in case further help is required