Announcing the SAVIYNT KNOWLEDGE EXCHANGE unifying the Saviynt forums, documentation, training, and more in a single search tool across platforms. Click HERE to read the Announcement.

Getting HTML Response when calling Saviynt API in Postman

SinghAtul
Regular Contributor
Regular Contributor

Hi all,

I have setup the Saviynt APIs in Postman and trying to call the 'GetUserDetails' API.

I am getting some HTML response stating "Sign in to your account".

I have followed all the guidelines and created the user which we are using to call the Saviynt API in Postman. I have set localAuthEnabled=1 and passwordexpired=0 for this user using CutsomQueryJob.

I am not sure why I am getting this message "Sign in to your account", as this user has the ability to bypass SSO.

This is what we get in Postman response:

SinghAtul_2-1685473756189.png

We are getting this HTML response for all APIs and not just getUserDetails API.

Note:

1). We are using Azure AD as the Identity provider.

2) We are currently in version 23.4

Please guide.

Thanks,

Atul Singh

 

6 REPLIES 6

dgandhi
All-Star
All-Star

Hope you passing the bearer token in your postman call. Please confirm.

 

Thanks,
Devang Gandhi
If this reply answered your question, please Accept As Solution and give Kudos to help others who may have a similar problem.

SinghAtul
Regular Contributor
Regular Contributor

@dgandhi 

Yes, we are passing the Bearer Token in the Authorization.

SinghAtul_0-1685508242842.png

 

SinghAtul
Regular Contributor
Regular Contributor

@dgandhi 

When we deactivated the SSO, we are getting the response as expected in Postman.

SinghAtul_0-1685553221273.png

From the above, we can see that the localAuthEnabled is already set to true for this user (the user we are using to call the Saviynt API). Also, passwordexpired is set to false.

Still, this user is not able to bypass the SSO. We had completely deactivate the SSO in order to work with the Saviynt APIs.

Is there some setting we are missing? Or is there something that needs to be configured at Azure end?.

Please advice.

Thanks.

Have you checked this URL?

https://docs.saviyntcloud.com/bundle/EIC-Admin-v23x/page/Content/Chapter06-EIC-Configurations/Config...

 

Thanks,
Devang Gandhi
If this reply answered your question, please Accept As Solution and give Kudos to help others who may have a similar problem.

Rajesh-R
Saviynt Employee
Saviynt Employee

This is expecting Security question to be set (for the user we are using to call the Saviynt API)

There is a Global Configuration "Set Security Question on Login

  • If checked - it will expect a user to set the security questions and answers if not already done before the login.
  • If unchecked - it will not expect a user to set the security questions and answers if not already done before the login.

In this case - while calling getUser / getAccounts / getEndpoints / any api for that matter, it is expecting the security answers to be set (for the user we are using to call the Saviynt API).

Hence it is throwing a security questions reset page, but that page is protected, hence it throws the login page.

Two options here:

Option 1: Login with the user on the login page and set the security questions. Then try to access any API, it will work.

Option 2: Uncheck the Global Configuration "Set Security Question on Login". Then try to access any API, it will work.


Thanks
Rajesh Ramalingam
Saviynt India

BillyMai
New Contributor III
New Contributor III

Even with option 2 uncheck the "Set Security Question on Login" it still doesn't work.