---
sourceDocument: Brazil Sales Customer Relationship Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/order-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Sales Customer Relationship Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Single sign-on (SSO) integration

# Single sign-on (SSO) integration {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Single sign-on (SSO) integration

This guide explains how ServiceNow CPQ customers can integrate Single Sign-On (SSO) for headless use cases such as embedding CPQ on websites or eCommerce platforms.
It supports any identity provider (IdP) that uses OAuth2 with OpenID Connect (OIDC), but not SAML.
Integration requires submitting an SSO Setup Request Form with IdP details and user information.
The ServiceNow CPQ team then completes provisioning and assists with testing the redirect flow.
Show full answer Show less  

## Key Integration Steps

* Create an application for ServiceNow CPQ in your chosen IdP.
* Share app parameters (client ID, client secret, redirect URI, and domain) and user details with the ServiceNow CPQ team.
* The team schedules a call to securely obtain your client secret and complete provisioning.
* Test the SSO redirect flow to confirm users are directed to the IdP consent screen and can authenticate successfully.

Note: Users added before SSO implementation may need to be re-added. This process is unnecessary if using ServiceNow CPQ with Salesforce.

## Configuring Popular IdPs

### Google SSO

Supports both personal and business Google accounts. Only user names and email addresses are required for setup.

### Okta SSO

* Use Okta Developer instructions to create an app with Authorization Code Flow.
* Specify the redirect URL as your ServiceNow CPQ URL with the suffix `/login/oauth2/code/<your-subdomain>-okta`.
* Confirm the Okta domain by checking the openid-configuration metadata endpoint.
* Provide client ID, client secret, redirect URL, Okta domain, and user emails to the ServiceNow CPQ team.
* Email addresses used for authentication are case sensitive---accuracy is critical.
* After setup, verify the redirect to the Okta consent screen upon accessing your tenant-specific CPQ URL.

### Microsoft Entra ID SSO

* Register a web application in Microsoft Entra ID and set the redirect URI as your tenant-specific URL appended with `/login/oauth2/code/<your-subdomain>-entra`.
* Enable ID tokens on the Authentication tab.
* Record client ID, client secret (not retrievable later), and Authority URL (including `/v2.0` suffix) for validation.
* Optionally associate users via Microsoft Entra portal and assign app roles for testing.
* Submit client ID, Authority URL, redirect URI, and user details via the SSO Setup Request Form.
* The ServiceNow CPQ team schedules a call to collect the client secret and complete provisioning.
* Test authentication by accessing the tenant-specific CPQ URL, which should redirect to the Entra ID consent screen.

### Troubleshooting Common Issues

* **Issuer mismatch:** Ensure the issuer URL ends with `/v2.0` and set `accessTokenAcceptedVersion` to 2 in the app manifest.
* **Unexpected redirect to logik.ai:** Set `acceptMappedClaims` to true in the manifest.

## Configuring Other IdPs

ServiceNow CPQ supports any IdP compatible with OAuth2 and OIDC. Submit your IdP details in the SSO Setup Request Form, and the ServiceNow CPQ team will coordinate integration and testing.  
If you intend to use ServiceNow CPQ for a headless use case (such as exposing ServiceNow CPQ on a website or eCommerce platform), please fill out and submit an SSO Setup Request Form that details the identity provider (IdP) you are using for single sign-on (SSO).
This process involves:

* Creating an app for ServiceNow CPQ in your IdP tool of choice. See the steps and links below.
* Sharing parameters and users from the app with the ServiceNow CPQ team. The team will complete the provisioning process using the parameters that you send.
* Testing and confirming that the SSO redirect works as expected.

{#cpq-single-sign-on-sso-integration__ul_xvm_lyx_23c}

Note the following considerations:

* ServiceNow CPQ can now support SSO with any IdP that supports OAuth2 with OpenID Connect (OIDC).
* ServiceNow CPQ is not compatible with SAML.
* Your IdP client must be up to date.
* Users who have been added to ServiceNow CPQ before SSO was implemented may need to be added again.
* These steps are not required if you are using ServiceNow CPQ with Salesforce.
{#cpq-single-sign-on-sso-integration__ul_fvl_qyx_23c}

## Configuring Google SSO {#cpq-single-sign-on-sso-integration__section_zvc_xyx_23c}

ServiceNow CPQ supports Google for both personal and business single sign-on. If you use Google IdP for identity verification, all we need are the names and email addresses of your users.

## Configuring Okta SSO {#cpq-single-sign-on-sso-integration__section_vbw_yyx_23c}

To set up an application that supports the Authorization code flow for ServiceNow CPQ, start by following the Okta Developer instructions: [Implement authorization by grant type: set up your app](https://developer.okta.com/docs/guides/implement-grant-type/authcode/main/#set-up-your-app)

For the redirect URL, specify your ServiceNow CPQ URL, append `/login/oauth2/code/`, and then append your `-okta` subdomain. So if your URL is `example.test.logik.io`, your redirect URL would be
`https://example.test.logik.io/login/oauth2/code/example-okta`.  
Note your client ID, client secret, redirect URL, and Okta domain.  
Note:  
To confirm that your Okta domain is accurate, you can confirm that the OpenID connection metadata is visible by visiting `https://{oktaDomain}/.well-known/openid-configuration`. You should see a JSON file with information about the authorization server endpoints.  
Provide these values together with any user details, such as name and email, for users that you want to test with. The ServiceNow CPQ team will schedule a brief call with you to obtain your client secret. The team will complete the provisioning process from there.  
Note:  
Users' email addresses will be used for authentication. These are case sensitive, so make sure that the email addresses you provide are accurate.

When your ServiceNow CPQ point of contact has confirmed that setup is complete, try to visit your tenant-specific ServiceNow CPQ URL. You should see a redirect flow that brings you to an Okta consent screen to allow access to your ServiceNow CPQ app.

## Configuring Entra ID SSO {#cpq-single-sign-on-sso-integration__section_r15_xyx_23c}

Register an app by following the instructions on the following Microsoft Entra documentation website:

[Register an application in Microsoft Entra ID](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app)

In the Redirect URI section of the Microsoft Entra registration page, in the Select a platform menu, select Web. For the redirect URI, enter your tenant-specific
URL, append `/login/oauth2/code/`, and then append `<your subdomain>-entra`. For example, if your URL is `example.test.logik.io`, your redirect URI is
`https://example.test.logik.io/login/oauth2/code/example-entra`.

Make sure to select ID tokens on the Authentication tab of your app. For more information about OIDC, see the following Microsoft Entra documentation website: [OpenID Connect on the Microsoft identity platform](https://learn.microsoft.com/en-us/entra/identity-platform/v2-protocols-oidc).  
Note your client ID, client secret, and your Authority URL.  
Note:  
Make sure you note the client secret at this time. It won't be available to you later.
For information about how to validate your Authority URL, see "Find your app's OpenID configuration document URI" at the Microsoft Entra documentation website: [OpenID Connect on the Microsoft identity platform](https://learn.microsoft.com/en-us/entra/identity-platform/v2-protocols-oidc). To get the correct issuer in the metadata, make sure to include `/v2.0` at the end. You should be able to see the metadata and validate your issuer URL by visiting it in a browser with `/.well-known/openid-configuration` appended to it. For example: `https://login.microsoftonline.com/c7dd9346-1cfc-4bd8-a34c-a066c8bc0477/v2.0/.well-known/openid-configuration`.  
Note:  
It may be possible to directly associate your users with the application via the ManagerUsers and groupsAdd user/group option in your application.

Optionally, add an app role for the users whom you wish to test with. For more information, see "Add a user account to your directory, and add that account to an appRole" on the following Microsoft Entra documentation website: [Add sign-in with Microsoft Entra account to a Spring web app](https://learn.microsoft.com/en-us/azure/developer/java/spring-framework/configure-spring-boot-starter-java-app-with-entra?toc=/entra/identity-platform/toc.json&bc=/entra/identity-platform/breadcrumb/toc.json#create-microsoft-entra-instance)

On the SSO Setup Request Form, provide the client ID, Authority URL, and redirect URl together with user details (email, name) for the users you wish to test with. The ServiceNow CPQ team will schedule a brief call with you to obtain your client secret.

By default, each user's emails will act as their identifiers, but it may be possible to use a different identifier in a user profile. The fields that can be used as identifiers are limited by what's available at the
`user_info` endpoint defined in the well-known/openid-configuration URL described above. For more information about the `user_info` endpoint, see the following Microsoft Entra documentation website: [Microsoft identity platform UserInfo endpoint](https://learn.microsoft.com/en-us/entra/identity-platform/userinfo).

Once your ServiceNow CPQ point of contact has confirmed that setup is complete, try to visit your tenant-specific ServiceNow CPQ URL. You should see a redirect flow that brings you to an Entra ID consent screen to allow access to your ServiceNow CPQ app.
{#cpq-single-sign-on-sso-integration__table_rhp_c2y_23c__entry__2}

| Issue | Resolution |
|-|-|
| The issuer does not match the expected value. For example, the issue is `sts.microsoft.net` instead of `login.microsoftonline.com`. | * Make sure that your issuer URL includes `/v2.0` after the tenant ID. * Update the application manifest to set the accessTokenAcceptedVersion to 2. {#cpq-single-sign-on-sso-integration__ul_zc1_g2y_23c} |
| Admin is redirected to http://logik.ai, despite being set up correctly. | In your manifest, set the acceptMappedClaims parameter to true in your manifest. |
[Table 1. Troubleshooting]

{#cpq-single-sign-on-sso-integration__table_rhp_c2y_23c}

## Configuring another IdP {#cpq-single-sign-on-sso-integration__section_pp1_1zx_23c}

ServiceNow CPQ can now support SSO with any IdP that supports OAuth2 with OpenID Connect (OIDC). In the SSO Setup Request Form, provide details about your preferred IdP tool and our team will connect with you to ensure it is
properly integrated with ServiceNow CPQ.

*[\>]: and then


