How to authenticate SailPoint IIQ Out-of-the-box API's using OAuth 2.0 Client Credentials instead of Basic Auth

IdentityIQ (IIQ) IIQ Discussion and Questions
, ,
1

Which IIQ version are you inquiring about?

v8.3 p3

Please share any images or screenshots, if relevant.

image
image696×362 33.8 KB

Share all details about your problem, including any error messages you may have received.

We are using SailPoint Scim APIs to pull information from SailPoint instance. Recently a requirement has been added stating a need to change the API authentication type from Basic Auth to Oauth2.0. While searching more on the community we came across the steps to generate the OAuth client credentials in SailPoint IdentityIQ and an API endpoint to generate the authorization access token using OAuth Client credentials.

While we have been able to create the Client Credentials in our SailPoint Instance, we are facing challenges in constructing the access token generation API call as we do not see any documentation for this API on SailPoint compass.

API: “http://localhost:8080/identityiq/oauth2/token”

Help appreciated with any type of information on the construction of this API including required headers, body data, params, etc.

2

Hey @tthakar,

it would be helpful if you can share more details or http response you get.

Here is example of working request:

image
image1051×978 61.6 KB

Green(identityiq)
Black(secret)

3

Hi @abartkowski,

Actually we lack information about constructing this specific API, that is why this post was created.

Going further based on your suggestion I have tried building it similar in Postman (Auto-generated Curl code visible aside in screenshot).

But it looks like it ain’t working. (screen-snip added below)

Appreciate your help.

image
image1918×753 58.8 KB

Amber (Client ID)
Blue (Client Secret)

Thank You in advance!

4

Hey @tthakar

please check under settings for this request if the option with SSL is off.

image
image1495×277 27.8 KB

5

Hello @abartkowski,

Yes it’s turned off.

image
image666×880 110 KB

6

Hey @abartkowski,

Well I changed the protocol from HTTPS to HTTP and the API call just worked.

BUT now it is a 400, not sure what’s wrong on the config as I tried to replicate what you suggested.
I’m still using No Auth as the Auth type.

image
image1913×426 58.3 KB

7

Are you sure that your IdentityIQ instance is configured such that ‘identityiq’ follows ‘localhost:8080/’? A ‘Bad Request’ error does not sound good. :smiley:

8

Yes @abartkowski ! It is the correct path.