Passing Additional headers in SCIM 2.0 Token based authentication

[Arshad (Arshad Moghul)]

Hi All,

I am integrating an application using SCIM 2.0 connector with a Basic Authentication method.

For this authentication, from the application side we have a few mandatory additional headers which need to pass.

The connector documentation mentions that additional headers can be added to the XML only if the authentication mechanism is OAuth 2.0 in the UI config. But in my case, I am using Basic Authentication in the UI and when tried to add the below statement to the Application XML from debug, the test connection still fails:

<entry key="BasicLogin">
<value>
<Map>
<entry key="api_key" value="testapikeyvalue"/>
</Map>
</value>
</entry>

Has someone come across this requirement and kindly help with any suggestions?

Thanks in advance,
Arshad.

[brian_weigel]

You will probably need to configure it as No Authentication and use the noAuthHeaders app config key to define the needed authentication: No Authentication - Send Custom Headers in the Request Body

[Arshad (Arshad Moghul)]

Hi @brian_weigel

Thank you for the feedback. I tried the No Authentication way with noAuthHeaders in the app config.

The test connection doesn’t work still.

[brian_weigel]

By “still doesn’t work”, I assume you are referring to the same HTTP 403 error in your screenshot?

[Arshad (Arshad Moghul)]

Hi @brian_weigel

Thanks for the turn around. I’ve figured the solution for this one.

To achieve SCIM 2.0 connectivity with additional headers using basic authentication, what we need to do is select No Authentication as the “Authentication Type” in the app config UI.

Below is the block that I’ve added to the application XML:

<entry key="noAuthHeaders">
    <value>
        <Map>
            <entry key="Authorization" value="Basic [encrypted id and password value which you can obtain from Postman collection by exporting the API call to a curl command]"/>
            <entry key="[Additional_Header_Name]" value="[Header_Value]"/>
        </Map>
    </value>
</entry>

Now, the connectivity will be established without any issues.

@brian_weigel , the mistake I did previously was to just add the id and password as separate entries in the above XML instead of adding the Authorization key and encrypted User ID/Password value from postman collection.

Regards,
Arshad.