My team is trying to set up a web services connector to SuccessFactors. For reasons I will not go into, we can not rely on the out of the box SuccessFactors connector.
The connection requires Authentication Type OAuth 2.0 and Grant Type SAML Bearer Assertion.
We managed to establish the connection with custom authentication and in Postman but would like to transition the authentication method to use the OAuth 2.0.
I believe I’ve managed to figure out what most of the fields shall be filled out with.
However, the “SAML Request Body” is a question mark and the documentation is not sufficient: OAuth 2.0 Authentication
If anyone has managed to configure a web services connection with OAuth 2.0 and SAML Bearer Assertion, please enlighten me how you accomplished it.
You have to use the custom authentication along with after operation rule to generate assertion and to pass the assertion to token url.
Custom authentication for SAML Assertion
In the body key and values by using Form data
Header is Content-type. - application/x-www-form-urlencoded
Use after operation rule to get response object
Rule-
Map m new HashMap();
m.put(“assertion”,assertionVal);
processedResponseObject(m);
In response mapping
aschema Attribute is assertion - attribute path is $rawResponseObject$
Custom authentication to get token
Header is Content-type. - application/x-www-form-urlencoded
Provide token generation details into the body by selecting Raw type
In response mapping read token
Schema attribute is access_token and attribute path is access_token
For test connection and other operations use Bear $application.access_token$
I’ve managed to use raw body in Postman like this:
client_id={{client_id}}&user_id={{user_id}}&token_url=https%3A%2F%2F{{api-server}}%2Foauth%2Ftoken&private_key={{private_key}}
You can also follow the same in SailPoint ISC as well. Keep all the required information in the Custom Authentication Operation body by selecting the raw. But make sure need to add headers should be application/x-www-form-urlencoded.
If you try the same by selecting Oauth2.0 it won’t work.
I don’t have any document. But for the same issue i connected with SailPoint support team they mentioned the same.
