We are working with the Web Services (SaaS) connector. Our authentication REST API token endpoint returns the access token directly as a plain/JWT string (for example: “abcsjjdk–d”) rather than as a JSON object.
In SailPoint ISC, the connector typically expects a JSON response and allows token extraction using a JSONPath such as $application.accessToken$. However, since our token endpoint returns only the raw token string this approach does not work for us.
After reviewing forum responses, we switched to the Custom Authentication option. We are still trying to understand how to correctly map the token in the Test Connection response mapping and then pass that token into the Create User HTTP operation for authorization?
You could use a web service before operation rule to execute the get token call. You’d get your credentials from the application class, make a call to the token endpoint using the restClient class, then add the access token to the request headers using the requestEndPoint class
EDIT: I just realized this is a web services SaaS connector which doesn’t use the before/after operation rules like the VA-based one does. For that you’d have to use some sort of endpoint customizer to make this work
Also I was going through SailPoint documentation under Custom Authentication, I tried adding an attribute to the connector and storing the complete token response in that attribute. However, not sure whether this is actually possible. If anyone has any insights or experience with this approach?