# SCIM 2.0 Connector OAuth 2.0 Configuration, Test connection getting failed

**URL:** <https://developer.sailpoint.com/discuss/t/scim-2-0-connector-oauth-2-0-configuration-test-connection-getting-failed/186332>\
**Category:** IIQ Discussion and Questions\
**Tags:** identityiq\
**Created:** [October 24, 2025, 4:49pm UTC](https://developer.sailpoint.com/discuss/t/scim-2-0-connector-oauth-2-0-configuration-test-connection-getting-failed/186332 "2025-10-24T16:49:40Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![venumgm235](https://avatars.discourse-cdn.com/v4/letter/v/87869e/32.png) [@venumgm235](https://developer.sailpoint.com/discuss/u/venumgm235)\
**Post date:** [October 24, 2025, 4:49pm UTC](https://developer.sailpoint.com/discuss/t/scim-2-0-connector-oauth-2-0-configuration-test-connection-getting-failed/186332/1 "2025-10-24T16:49:40Z")

</div>

## Which IIQ version are you inquiring about?

_8.4p3_

## Please share any images or screenshots, if relevant.

 ![Annotation 2025-10-22 101508](https://global.discourse-cdn.com/sailpoint/original/3X/3/6/36ed7fccba6fbefa387180fa5a75bbe88e9775a8.png)

## Share all details about your problem, including any error messages you may have received.

The Authentication is a bit different compare to OAuth 2.0, If we observe the below curl, we need to pass the client\_id and secret as Basic authentication and need to pass urlencoded values and scope, but it’s not working i tried below entries in application XML, but still getting failed

```auto
<entry key="oauth_headers">
<value>
<Map>
<entry key="Content-Type" value="application/x-www-form-urlencoded"/>
</Map>
</value>
</entry>
<entry key="oauth_request_parameters">
<value>
<Map>
<entry key="grant_type" value="client_credentials"/>
<entry key="scope" value="urn:opc:idm: __myscopes__"/>
</Map>
</value>
</entry>

```

curl --location ‘[https://iXXXXXXX/oauth2/v1/token](https://ixxxxxxx/oauth2/v1/token)’ \  
–header ‘Content-Type: application/x-www-form-urlencoded’ \  
–header 'Authorization: Basic XXXXXX \  
–data-urlencode ‘grant\_type=client\_credentials’ \  
–data-urlencode ‘scope=urn:opc:idm:\__myscopes_\_’

@officialamitguptaa

---

<div class="post-metadata">

**Author:** ![kumarSinghM](https://avatars.discourse-cdn.com/v4/letter/k/ecb155/32.png) [@kumarSinghM](https://developer.sailpoint.com/discuss/u/kumarSinghM)\
**Post date:** [October 24, 2025, 5:53pm UTC](https://developer.sailpoint.com/discuss/t/scim-2-0-connector-oauth-2-0-configuration-test-connection-getting-failed/186332/2 "2025-10-24T17:53:38Z")

</div>

Use Before operational Rule to generate access token and do the connection.

---

<div class="post-metadata">

**Author:** ![venumgm235](https://avatars.discourse-cdn.com/v4/letter/v/87869e/32.png) [@venumgm235](https://developer.sailpoint.com/discuss/u/venumgm235)\
**Post date:** [October 24, 2025, 6:08pm UTC](https://developer.sailpoint.com/discuss/t/scim-2-0-connector-oauth-2-0-configuration-test-connection-getting-failed/186332/3 "2025-10-24T18:08:25Z")

</div>

Hello Manish,  
My bad, it’s not for Webserivce, it’s for SCIM 2.0 connector. i am getting this issue

---

<div class="post-metadata">

**Author:** ![kumarSinghM](https://avatars.discourse-cdn.com/v4/letter/k/ecb155/32.png) [@kumarSinghM](https://developer.sailpoint.com/discuss/u/kumarSinghM)\
**Post date:** [October 24, 2025, 6:14pm UTC](https://developer.sailpoint.com/discuss/t/scim-2-0-connector-oauth-2-0-configuration-test-connection-getting-failed/186332/4 "2025-10-24T18:14:31Z")

</div>

This is not a combination of SCIM 2.0 and Logiplex connector?

---

<div class="post-metadata">

**Author:** ![kumarSinghM](https://avatars.discourse-cdn.com/v4/letter/k/ecb155/32.png) [@kumarSinghM](https://developer.sailpoint.com/discuss/u/kumarSinghM)\
**Post date:** [October 24, 2025, 6:15pm UTC](https://developer.sailpoint.com/discuss/t/scim-2-0-connector-oauth-2-0-configuration-test-connection-getting-failed/186332/5 "2025-10-24T18:15:21Z")

</div>

Because when I configured a Logiplex connector with SCIM 2.0 as master app then I faced this type of problem.

---

<div class="post-metadata">

**Author:** ![venumgm235](https://avatars.discourse-cdn.com/v4/letter/v/87869e/32.png) [@venumgm235](https://developer.sailpoint.com/discuss/u/venumgm235)\
**Post date:** [October 24, 2025, 6:16pm UTC](https://developer.sailpoint.com/discuss/t/scim-2-0-connector-oauth-2-0-configuration-test-connection-getting-failed/186332/6 "2025-10-24T18:16:46Z")

</div>

> [@kumarSinghM](#):
>
> combin

No, it’s not a combination, of logiplex connector, it’s only configured with SCIM 2.0

---

<div class="post-metadata">

**Author:** ![venumgm235](https://avatars.discourse-cdn.com/v4/letter/v/87869e/32.png) [@venumgm235](https://developer.sailpoint.com/discuss/u/venumgm235)\
**Post date:** [October 24, 2025, 6:19pm UTC](https://developer.sailpoint.com/discuss/t/scim-2-0-connector-oauth-2-0-configuration-test-connection-getting-failed/186332/7 "2025-10-24T18:19:05Z")

</div>

The authentication mechanism is a bit different compare to other OAuth, here i need to pass client id and secret as basic auth, but with the default configuration no option to pass them as basic auth for token generation.

I am able to generate the token from Postman with the curl that shared

---

<div class="post-metadata">

**Author:** ![kumarSinghM](https://avatars.discourse-cdn.com/v4/letter/k/ecb155/32.png) [@kumarSinghM](https://developer.sailpoint.com/discuss/u/kumarSinghM)\
**Post date:** [October 24, 2025, 6:26pm UTC](https://developer.sailpoint.com/discuss/t/scim-2-0-connector-oauth-2-0-configuration-test-connection-getting-failed/186332/8 "2025-10-24T18:26:51Z")

</div>

Try using a web service connector and write before operational rule to handle this connection scenarios in each operation if it is not supported in SCIM connector.

---

<div class="post-metadata">

**Author:** ![venumgm235](https://avatars.discourse-cdn.com/v4/letter/v/87869e/32.png) [@venumgm235](https://developer.sailpoint.com/discuss/u/venumgm235)\
**Post date:** [October 24, 2025, 7:53pm UTC](https://developer.sailpoint.com/discuss/t/scim-2-0-connector-oauth-2-0-configuration-test-connection-getting-failed/186332/9 "2025-10-24T19:53:49Z")

</div>

Hi Manish,

I verified all the default API’s related to SCIM all are fine, so only problem with authentication. If the authentication works, there is no need of any additional development required to onboard this application so if i go with Webservice more dev work is required, so checking if we can customize the authentication mechanism in SCIM.

---

<div class="post-metadata">

**Author:** ![venumgm235](https://avatars.discourse-cdn.com/v4/letter/v/87869e/32.png) [@venumgm235](https://developer.sailpoint.com/discuss/u/venumgm235)\
**Post date:** [October 28, 2025, 4:51pm UTC](https://developer.sailpoint.com/discuss/t/scim-2-0-connector-oauth-2-0-configuration-test-connection-getting-failed/186332/10 "2025-10-28T16:51:25Z")

</div>

Hi @Arshad , could you please check on this post, is there anyway that we can build a custom authentication for this type request

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [December 27, 2025, 4:51pm UTC](https://developer.sailpoint.com/discuss/t/scim-2-0-connector-oauth-2-0-configuration-test-connection-getting-failed/186332/11 "2025-12-27T16:51:31Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.