---
sourceDocument: Brazil Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-security

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# SCIM Troubleshooting

# SCIM Troubleshooting {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Common errors that occur when you integrate with SCIM.

## Invalid REST API URL {#scim-troubleshooting__section_o3r_sch_ywb}

Action: Enter valid API URL. You can check the REST API URL in the REST API Explorer.

## No redirect URL is set in ServiceNow instance {#scim-troubleshooting__section_cbd_2dh_ywb}

Action: Enter valid Redirect URL for SCIM OAuth entity in ServiceNow. Enter redirect URL while you configure the OAuth entity in ServiceNow.

## When the redirect URL is different from the request {#scim-troubleshooting__section_wm3_hdh_ywb}

Action: 'redirect_url' provided in 'Authorization Endpoint' should be the same as the OAuth entity configured in ServiceNow.  
Note:  
This error occurs when there is a mismatch between Azure 'Authorization Endpoint' and ServiceNow 'Redirect URL'

## When an invalid client secret is passed {#scim-troubleshooting__section_bpn_ldh_ywb}

Action: Value entered in 'Client Secret' should be the same as the OAuth entity configured in ServiceNow.

## When an invalid client ID is passed in Azure Authorization Endpoint {#scim-troubleshooting__section_nzk_rdh_ywb}

Action: Value entered for 'client_id' parameter in 'Authorization Endpoint' must be the same as the OAuth entity configured in ServiceNow.

