Share all details about your problem, including any error messages you may have received.
We are trying to integrate a REST based CRM On-Premises app with SailPoint IIQ 8.2 using the Web Services (REST) connector. The CRM API is secured with NTLM (Windows Authentication).
From our IIQ server, a direct CURL command using the --ntlm flag with the service account credentials works perfectly and returns the expected data — so connectivity and credentials are confirmed good.
The problem is on the IIQ side. When the same call is made through the REST connector, it fails with a 401. NTLM is not supported out of the box in the Web Services connector — there is no Authentication Type option for NTLM in the application configuration UI.
Has anyone successfully integrated an NTLM-secured REST API with SailPoint IIQ? If so, we would really appreciate knowing the approach — whether it was through a custom connector, a specific rule pattern, a reverse proxy in front of the API, or any other workaround.
Please try changing the Auth type to Custom Authentication and write a rule to authenticate. For every API call, IIQ will use this rule for authentication.
Custom Auth op is not helping in this scenario as it is mostly for capturing access/bearer token to be passed as a header or body attribute in subsequent calls.
However, NTLM is a 3 way handshake protocol which cannot be passed as a Bearer token or API key.
@Su_Kumar You mentioned curl command is working with --ntlm, right? So in Custom Auth, go to configuration and there is curl command option, have you already checked that?
