Hi
I have a webservice connector . Oath is established in postman. HOw to do it in sailpoint .
This should help
You can try:
Go to Connection Settings
Choose Authentication Type: OAuth 2.0
Grant Type: Password
Token URL: This is full URL to get token, probably ends in /oauth/token
Username: put username
Password: put password
OAuth Request Parameters:
Here you add the Client ID, Client Secret and Scope
For HTTP Operations, I believe it automatically sets the Authentication header, so you dont need to add it in.
Give that a try and see if your test connection works. Check the ccg.log for errors.
If that doesnt work, you may need to create Custom Authentication HTTP Operation.
Then you would set “bearer $application.accesstoken$” Authorization header in the HTTP Operations
Did you set your response mapping in your custom authentication?
Schema Attribute = accesstoken
Attribute Path =
Try changing you content-type to application/json
Hi @kani1 what error are you getting for the failure of connection?
Hi
Exception occurred while generating access token
Could you please share us the POSTMAN response body by masking sensitive info for generating access token?
Hope the config for custom auth operation is as follows:
Response information–> Root path–>$
Response mapping–>accesstoken = $.access_token
Also are you passing username and password in body of custom auth operation?
Hi ,
There is no body for custom authentication in Webservice saas connector
Select HTTP method as “POST”
Hi @kani1 ,
Here are my thoughts:
In the custom authentication screenshot, please remove the value in the context URL and give only the CustomAuthenticationURL(that ends with /connect/token).
Here is a way that I found to debug such issues
- Since this worked in Postman, expand the code snippet(</>) section.
- Select the ‘cURL’ format.
- Copy each parameter precisely as they appear in the respective sections on the UI.
In my case:
this is what I see in the Postman.
location is taken to CustomAuthenticationURL
Authorization is taken to header
ContentType is taken to header
data-urlencode is taken to body(ones you change the HTTP method to POST, you will see a body)
Note: Many times, it so happened that, though I thought I did everything right, re-doing again following the above essential points helped me resolve the issue(and I could not go back and say what I did wrong)
Hope this helps
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.