SCIM 2.0 Connector OAuth 2.0 Configuration, Test connection getting failed

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Which IIQ version are you inquiring about?

8.4p3

Please share any images or screenshots, if relevant.

Annotation 2025-10-22 101508
Annotation 2025-10-22 101508901×503 23 KB

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

<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’ \
–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

2

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

3

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

4

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

5

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

6

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

7

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

8

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.

9

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.

10

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