How to pass additional headers in non compliant scim Connector using API Token authentication?

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

IIQ Version 8.2 P2

Hi , I have API token authentication working fine on 8.2 P2 for SCIM 2 connector.

However , I have to pass additional sec headers as part of the requirement .

I tried

<entry>
<value>
<Map>
<entry key="Authorization" value="Bearer tokenValue"/>
<entry key="someheader" value="somevalue"/>
</Map>
</value>
</entry>

The above is not working and giving me the error :

[ InvalidConfigurationException ] [ Possible suggestions ] Please check OAuth2 Token [ Error details ] 401

I unchecked non-compliant server and it started working , but since all the operations are not working as expected like create , update etc.,

Is there any alternate solution for SCIM 2.0 connector to pass additional security headers in the XML config or in the UI or before provisioning rule?

Thanks in Advance.

Keerthi

2

Based on similar SCIM configuration patterns, potential solutions include:

  1. Custom Authentication - Switch Authentication Type to “Custom” and use customizeRequest rule to inject headers programmatically (approach discussed here)

  2. beforeProvisioning Rule - Add headers in a beforeProvisioning rule that manipulates the request object before it’s sent

  3. Verify noAuthHeaders syntax - Ensure your XML structure matches the connector’s expected format for API token auth with additional headers

3

Hi Rakesh,

1.Custom Authentication is not available in SCIM V2.0 Connector Type. It is only available in WebServices Connector.

  1. BeforeProvisioningRule - RequestEndPoint and sending additional headers can be coded in Webservices before Provisioning Rule but not in SCIM Before Provisioning Rule because requestEndPoint is not available.
  2. I verified noAuthHeaders syntax and the test connection is successful when “Non Compliant “ checkbox is unchecked. However , My target is non compliant to scim standards and have to check that box for the remaining operations to be successful.

Please let me know if there is any known solution for Non compliant SCIM server with API Token authentication to pass additional headers.