WebService issue

Hi Team,

I was trying to onboard Zuora in IdentityNow, however I am encountering an error whenever I try to Test Connect.
Error: " Error Received:
Exception occurred in Test Connection.Url: https://one.zuora.com/oauth2/token, Message: 302 : Unknown Error, HTTP Error Code: 302"

Not really sure which HTTP Operation is the problem as I have a custom authentication operation and it’s the same with the ones we onboarded back then.

Can anyone help me pls.

Thanks!

Hey @CeeJ1,

Based on the message, “Test Connection” operation is failing. Could you check if the API call that are configured in Test Connection operation is working through Postman?

Hi @zeel_sinojia, yes it’s working in Postman.

And this is how it’s being configured in the HTTP Operation

Hello @CeeJ1,

This seems to be an issue with the authentication, since the authtoken URL is shown. HTTP Response Code 302 is typically received when an API has moved to a new endpoint. Could you give your authentication request a try in Postman or another tool to see if it is still valid?

Hi @bcariaga, it’s still working

Can you post some snapshots of the Custom Authentication operation that you have configured in SailPoint?

Mostly want to look at the URL, headers and body of that request. Please hide any password/secrets.

Hi @CeeJ1,

Seems like issue with your custom authentication HTTP operation.

Make sure your response mapping is correct and using the same in other HTTP operations (in header) like test connection.

Regards,
Shekhar Das

1 Like

Here:




1 Like

@CeeJ1 please validate the configuration using below document:

Custom Authentication (sailpoint.com)

2 Likes

Hi @CeeJ1 ,

can you try using the cURL from postman and use it in the Custom Authentication, and please change Attribute path from $.access_token to access_token and put $ in Root path of Response information.

Thank you

1 Like

Hi,

I’m getting this error after using cURL and other changes

In the request body for custom authentication, did you remove value for grant_type?

it should be in format grant_type=GRANT_TYPE&client_id=CLIENT_ID&client_secret=CLIENT_SECRET.

Hi @zeel_sinojia,
I checked that too looks like I missed that part out but when I fixed to test connect I’m still getting the 401 error

Could you paste here the cURL command that you are using now? Also try if the normal operation works now that you have updated your request.

@CeeJ1 this means your custom authentication is now fine.

This is going to test connection http operation, please make sure you are passing the variable correctly in test connection header.

I mean the variable you set in custom authentication for access token.

Also please check the context URL that going to different endpoint.

Hi @shekhardas1825, upon checking its passing the correct token and header is the same with what is in the postman. But I’m still getting the same error.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.