Configure OIDC applications

Information:

Cross Identity supports NONCE parameter for OIDC applications.

Configure OIDC Application

1. Navigate to Applications from the menu. Click + Add Application.

   

2. In the AppStore pane, click OIDC to view apps. Example- OIDC App Auth Code.

   

3. Select the application and it will take you to the Application Configuration page.

   

4. Configure the application using the following:

   • Application Name: It is a pre-filled text field. The name can be edited as per requirement. 

   • Application Logo: Upload a logo for the application or select the default logo available on the user's system. 

   • Client Identifier: The client ID is generated automatically when an application is onboarded from the App Store. It is the application's username, communicating with Cross Identity.

   • Client Secret: When an application is onboarded from the app store client secret key is generated. This client secret is a Password for the application to communicate with Cross Identity.

   • Enable refresh token: Select this field to refresh the token after the configured time.

   • Refresh Token Lifetime (minutes): Specify the lifetime to refresh the application token after the configured time the token refreshes. By default, it is set to 3 minutes.

   • Grant Type: The following grant types can be assigned to the target applications while configuring:

     Authorization code	A temporary code clients use to exchange an authorization code for accessing tokens.
     Implicit	It is a way for a single-page JavaScript app to get an access token without an intermediate code exchange step.
     Client Credential	It is used by clients to get access tokens to access their resources.
     Resource Owner Password Grant	It is used where the resource owner has a trust relationship with the client, such as the device operating system or a highly privileged application.

   • Access Token Lifetime (Seconds): Specify the OAuth access token time in seconds. By default, it is set to 3600 seconds.

   • Add URL: Click Add URL button and specify the URL. You can add multiple URLs.

     Note:

     Click on the link to configure Native App SSO.

   • Remove URL: Select the URL you want to delete and click the Remove URL button.

   • View Endpoints: Click View Endpoints to view the available endpoints:

     • Authorization Endpoint

     • Token Endpoint

     • UserInfo Endpoint

     • Token Introspection Endpoint

     • Token Revocation Endpoint

     • Refresh Token Endpoint

5. Click Save. The "Successfully associated provisioning application" confirmation message is displayed.

Scope

You can configure multiple scopes; Scope can be any attribute OAuth accepts it takes as a basis to Identify.

1.  Navigate to Scope. The screen is displayed.

   

2.  Click Add Scope. 

   

3.  Select the Scope Value from the drop-down and provide the Scope Description.

4. Click Add and the “Scope added successfully” confirmation message is displayed.

To remove a scope:

1. Click Remove Scope. 

2. Select a scope to delete.

3.  "Do you want to remove the selected scope" a confirmation message is displayed.

4. Click Remove. It will confirm that "Scope removed successfully."

Attribute Mapping

You can map Cross Identity attributes to the third-party application (For Example, Salesforce). These third-party application attributes are defined in the User Schema Attributes tab which is part of Advanced Screen.

1. Navigate to Attribute Mapping.

   

2. Map Profile attributes with User Attributes and click Save. A confirmation message is displayed.

Application Authorization

 You can add roles and users and authorize them to access the applications.

Authorize Roles

As an administrator, CI allows you to select specific roles authorized to access an application. 

To authorize roles, follow the steps: 

1. Navigate to Application Authorization. The application authorization screen is displayed.

   

2. Click Authorize Role > Add Role. The Add Role screen is displayed.

   

3. Enter a Role Name in the search field 

4. Select a role from the results and then click Add. 

5. The added role is displayed on the screen. 

   Information:

    Based on the role type, it allows the user to select either static or dynamic.

Authorize Users

As an administrator, CI allows only specific users to access the application. 

To authorize users, follow the steps: 

1. Click Authorize Users > Add User.

   

2.  Enter a username in the search field.

3. Select a user from the results and then click Add. 

   

4. The added user is displayed on the screen.

   Information:

   You can remove users from the Remove User tab.

License

This applies to the pay-per-use model, where the admins can assign a specific number of licenses for use in SSO. This prevents over-utilization of the application. 

1. Navigate to License.

2. Max. User Licenses: Enter the maximum number of licenses which can be issued to the application.

3. Application License Price: Enter the price for each license to calculate the total cost and displayed it on the Consumption Dashboard. 

   

4.  Click Save.

Application Security

You can set up multi-level authorization to improvize the security level. All SSO applications can have an additional parameter defined by an administrator.

To set up multi-level authorization:

1. Navigate to Application Security.

   

2. Check the box Enable Step-Up Authentication.

3. Select an authentication method:

   Field Name	Description
   Security Questions	Users must answer all the available security questions displayed on the screen.
   SMS OTP	Users receive one-time passwords on their registered mobile numbers. A phone number is dynamically derived from the user's profile.
   Email OTP	Users receive one-time passwords on their registered email addresses. The email address will be dynamically derived from the user's profile.
   Soft-Token	Six-digit one-time passcode is generated on the Soft Token app on the user's mobile number. The user needs to enter the passcode for verification.

4. Click Save. The "Successfully updated application step-up authentication" confirmation message is displayed.

5. Whenever End-User tries to access the SSO application, they will be redirected to MFA for Authentication and Consent.

   

6. After the access is granted, the user will consent to access the Application. This will be verified from End-User->My Profile->Consent.

   

7. This is the Application Security from CI-Level to End-User Application.