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

[RAKRHEEM (Rakesh Bhati)]

@keerthip

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?

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