OAuth (Client Credentials) configuration in SailPoint Identity Now

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

Hi All,
We are integrating a webservice connector (Authentication type: OAuth2, Grant type: Client Credentials). Provided all the required configurations details in connection settings. But, We are getting the below mentioned error. Not sure whether we are missing something here. Any sample configuration screenshots for Client credential flow will be helpful.

Error screenshot:

image
image527×249 5.59 KB

Thanks,
Karthik Amperayani

2

Hi @vamperayani This seems to be a network issue. Did you tried test connection to the application from VA?

3

Is this SaaS based connector or VA? I suggest you stay away from SaaS based unless you know how the target APIs and connector work 100% and also Since you do not have logs for these, you will have to rely on sailpoint support for troubleshooting and you will not get much of it.

if its VA based, enable logging and verify what’s causing this :

Enable Connector Logging

Have you considered increasing communication time :

Timeout Errors and Settings

4

@vamperayani
Firstly if you are using a non SAAS based connector try to login to the VA and execute the curl command if it is success then this problem is not related to VA.
Please confirm once you check that

5

@vamperayani It seems you have permission/Firewall issue on application side. So please see if below thing working fine

  1. Check with postman you are able to get the user. use same configuration and pass similar header, use minimum attribute in schema so u will get some details.
  2. If point 1 is working from postman and not working from env then please go to VA and do telnet and see if this is working from there. Check the connectivity and check with network team as they will be able to get exact trace.
  3. If no error enable logs for connector
  4. Check with SailPoint support team if nothing working.

I hope you will be able to resolve this issue.

1 Like
6

Hi @vamperayani,

I think it’s probably firewall issue.
You may follow @mkumariaas suggestions.

-Vasanth

7

I would start with looking at connectivity to the api you are connecting to, is it on-prem(close to the va) or internet based?