# Authorization error when integrating ServiceNow Service Catalog with SailPoint ISC **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** identity-security-cloud, authorization, servicenow\ **Created:** [July 13, 2026, 3:33pm UTC](https://developer.sailpoint.com/discuss/t/authorization-error-when-integrating-servicenow-service-catalog-with-sailpoint-isc/216352 "2026-07-13T15:33:01Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![ravikiran\_ch](https://avatars.discourse-cdn.com/v4/letter/r/c5a1d2/32.png) [@ravikiran\_ch](https://developer.sailpoint.com/discuss/u/ravikiran_ch)\ **Post date:** [July 13, 2026, 3:33pm UTC](https://developer.sailpoint.com/discuss/t/authorization-error-when-integrating-servicenow-service-catalog-with-sailpoint-isc/216352/1 "2026-07-13T15:33:01Z")
I’m setting up the OAuth authorization flow between ServiceNow Service Catalog and SailPoint ISC, following the official documentation: [User Account Configuration](https://documentation.sailpoint.com/connectors/servicenow/service_catalog/help/integrating_service_catalog/user_account_configuration.html) **Steps completed:** - Created an API Client in ISC (Authorization Code + Refresh Token grant types, scope `sp:scopes:all`, redirect URL set to the ServiceNow instance) - Configured the OAuth provider/consumer settings in ServiceNow (Authorization URL, Token URL, Client ID/Secret, Redirect URL) **Issue:** When I navigate to the request page in Service Catalog, I get the following error: > _“An authorization error has occurred. Check the OAuth Authorization Flow information in the Identity Security Cloud for Service Catalog setup.”_ ![image](https://global.discourse-cdn.com/sailpoint/original/3X/8/d/8dcfb79784fdf3980d08089b23ca5271f4bbe077.jpeg) What could be the reason for this? Do I need to perform any additional steps apart from those mentioned in the document? Also, the ServiceNow admin doesn’t have admin privileges in SailPoint — could that be related to the issue? ---
**Author:** ![Bapu-Gogu](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/bapu-gogu/32/40049_2.png) [@Bapu-Gogu](https://developer.sailpoint.com/discuss/u/Bapu-Gogu)\ **Post date:** [July 13, 2026, 3:50pm UTC](https://developer.sailpoint.com/discuss/t/authorization-error-when-integrating-servicenow-service-catalog-with-sailpoint-isc/216352/2 "2026-07-13T15:50:33Z")
User Personal Access Token for SetUp and API management level credentials use for application registry. ![image](https://global.discourse-cdn.com/sailpoint/original/3X/8/a/8aa704bd3600ca356896000ab400efaefdb5e759.png) ---
**Author:** ![ravikiran\_ch](https://avatars.discourse-cdn.com/v4/letter/r/c5a1d2/32.png) [@ravikiran\_ch](https://developer.sailpoint.com/discuss/u/ravikiran_ch)\ **Post date:** [July 13, 2026, 3:51pm UTC](https://developer.sailpoint.com/discuss/t/authorization-error-when-integrating-servicenow-service-catalog-with-sailpoint-isc/216352/3 "2026-07-13T15:51:31Z")
Yes I have the above mentioned configurations in the setup page as well, still the issue remains ---
**Author:** ![Bapu-Gogu](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/bapu-gogu/32/40049_2.png) [@Bapu-Gogu](https://developer.sailpoint.com/discuss/u/Bapu-Gogu)\ **Post date:** [July 13, 2026, 4:09pm UTC](https://developer.sailpoint.com/discuss/t/authorization-error-when-integrating-servicenow-service-catalog-with-sailpoint-isc/216352/4 "2026-07-13T16:09:30Z")
My suggestion would be, you can re-SetUp servicenow catalog from step one. use same credential you have generated previouly. ---
**Author:** ![punna0001](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/punna0001/32/42011_2.png) [@punna0001](https://developer.sailpoint.com/discuss/u/punna0001)\ **Post date:** [July 14, 2026, 7:36am UTC](https://developer.sailpoint.com/discuss/t/authorization-error-when-integrating-servicenow-service-catalog-with-sailpoint-isc/216352/5 "2026-07-14T07:36:16Z")
Hello Ravi, since this error shows up while opening Manage Access itself, the authorization-code flow isn’t completing. I would focus on the OAuth config rather than correlation or request-side permissions. I would verify these values exactly: - Redirect URL in both the ISC OAuth client and ServiceNow Application Registry: `https://.service-now.com/oauth_redirect.do` - Authorization URL: `https://.identitynow.com/oauth/authorize` - Token URL: `https://.api.identitynow.com/oauth/token` - “OAuth app name for Authorization code flow” on the Setup page must exactly match the Name of the OAuth provider in ServiceNow Application Registry Also make sure the two credential sets aren’t mixed up. The ISC OAuth client (Authorization Code + Refresh Token, `sp:scopes:all`) goes into ServiceNow Application Registry. A separate [Personal Access Token](https://documentation.sailpoint.com/connectors/servicenow/service_catalog/help/integrating_service_catalog/conn_auth_code.html) generated by an ISC administrator goes into the PAT fields on the Service Catalog Setup page. The ServiceNow admin doesn’t need ISC admin access just to configure ServiceNow. But the user completing the authorization needs to be able to sign in to ISC, and the user accessing Manage Access needs the `x_sap_intidn.user` [role](https://documentation.sailpoint.com/connectors/servicenow/service_catalog/help/integrating_service_catalog/assign_roles.html) in ServiceNow. Once you have confirmed everything, go to System OAuth \> Manage Tokens, revoke the existing token for this provider, and open Manage Access again to kick off a fresh authorization. If it still fails, check ServiceNow’s outbound HTTP logs. The token response will tell you if it’s an `invalid_client`, redirect URI mismatch, or something else. ---
**Author:** ![chravikiran](https://avatars.discourse-cdn.com/v4/letter/c/58956e/32.png) [@chravikiran](https://developer.sailpoint.com/discuss/u/chravikiran)\ **Post date:** [July 14, 2026, 9:18am UTC](https://developer.sailpoint.com/discuss/t/authorization-error-when-integrating-servicenow-service-catalog-with-sailpoint-isc/216352/6 "2026-07-14T09:18:53Z")
By revoke the existing token ,what do you mean, can you please eloborate ---
**Author:** ![punna0001](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/punna0001/32/42011_2.png) [@punna0001](https://developer.sailpoint.com/discuss/u/punna0001)\ **Post date:** [July 14, 2026, 9:38am UTC](https://developer.sailpoint.com/discuss/t/authorization-error-when-integrating-servicenow-service-catalog-with-sailpoint-isc/216352/7 "2026-07-14T09:38:57Z")
Go to **ServiceNow \> System OAuth \> Manage Tokens** and check whether an OAuth token exists for the SailPoint provider and your user account. You may need a ServiceNow administrator to check this, since that module is normally admin-only. If a token is present, open it and select **Revoke Access**. Then open Manage Access again. This should start a fresh authorization flow and request a new token from ISC. If no token is present, you can skip this step. It likely means the authorization did not reach the point where ServiceNow successfully stored the token, so I would go back and verify the OAuth URLs, provider name, client ID and secret. ---
**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [September 12, 2026, 9:38am UTC](https://developer.sailpoint.com/discuss/t/authorization-error-when-integrating-servicenow-service-catalog-with-sailpoint-isc/216352/8 "2026-09-12T09:38:59Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.