oAuth 2.0 - Postman - There is no access token in response body even though API call is successful.

Report · Mar 20, 2023

I am using developer account with free plan.
I am testing AdobeSign API to integrate with my company's product.
I cannot get access token with oAuth 2.0 in Postman.
I followed this article, and authorization is passed but response does not include access_token.

Shard is jp1.
https://helpx.adobe.com/sign/kb/how-to-create-access-token-using-postman-adobe-sign.html#:~:text=Log....

Do I need an enterprise account to get access token?

At lease integration key as access token is working to call API with free plan.

Report · Mar 31, 2023

Hi Keiji2755690106cb,

Thank you for reaching out.

As you have a question related to API integration, the experts can best answer it.

Moving this thread to the Acrobat Sign Developer board for visibility.

You may also contact the pre-sales team. They will be able to provide you the pre-sales technical assistance and share the correct information.

Please refer to the following link to contact them: https://acrobat.adobe.com/us/en/sign/pricing/plans.html. You may use the Contact us button for Adobe Sign Solutions under the team tab.

Thanks,

Meenakshi

Report · Apr 05, 2023

Hello,

Do you mean I need to purchase plan to get answer?

Thanks,

Keiji

Report · Apr 11, 2023

Hey Keiji2755690106cb,

As you are using the Developer account, the pre-sales team assists you with integration-related questions.

You may purchase the service when you require it.

Thanks,

Meenakshi

Report · Apr 12, 2023

Hi There,

You do not need an enterprise plan to be able to use oAuth.

The process is, however a bit exacting.

The response you are showing in the screenshot is HTML code which tells me that your request URL is probably not correct.

What is the URL you called when receiving this response, please?

Aaron Smusz - Data Science Engineering - Adobe Acrobat Sign

Report · Apr 12, 2023

Hi.

Auth URL: https://secure.jp1.adobesign.com/public/oauth/v2

Access token URL: https://secure.jp1.adobesign.com/public/oauth/v2/token

Best regards,

Keiji

Report · Apr 14, 2023

Even I am facing the same issue.

The Authorization was successful but the access point is not available in the response body.

Auth URL - https://secure.na3.adobesign.com/public/oauth/v2

Access Token URL - https://secure.na3.echosign.com/public/oauth/v2/token

Report · Apr 25, 2023

same issue here with same urls as rohith. after successful login/grant, the response is an html page, not the expected access token. Anyone getting any further?

using latest version of postman.

Report · Apr 26, 2023

I have the same issue. The error response as below

Report · Apr 26, 2023

I used as below

https://secure.na3.adobesign.com/public/oauth/v2

https://secure.na3.adobesign.com/public/oauth/v2/token

It seems the endpoint is really broken. There is nothing complex on token exchange endpoint process but it throws an HTML with a Security Violation and it does not let us know what the violation is.

Report · Apr 26, 2023

if you open the postman console, after you grant the access, you will see a number if requests. in my case, i see three requests. the first two are the expected oauth and token endpoints and the third is the user message endpoint which is an html page showing an error. the first two requests have 302 redirect responses. The first 302 response contains in the location header, your callback uri with a code= parameter. that is the secret code that you can use to retreive access and refresh tokens.

i believe that the second api call after user grants access is generating an error response for some reason, resulting in the second 302 redirect to the user message page, which i think hides the first 302 redirect to the redirect uri with the code parameter that we want to see. its there, you just have to hunt for it. i have used it to get access tokens.

i'm unclear though as to why the second call is redirecting to the user message error page. is that a real error? if so, it hasnt stopped me frim generating and using tokens to make api calls.

Report · May 05, 2023

Just to follow up, it seems that endpoint urls that work for me are

AuthURL: https://secure.na3.adobesign.com/public/oauth/v2

AccessTokenURL: https://secure.na3.adobesign.com/oauth/v2/token

Note that the AccessTokenURL has NO PUBLIC as part of its url while the AuthURL DOES. Setting these urls allows postman to work correctly when getting an access token. The second call will receive a 200 response instead of 302 redirect to a user error page and will allow postman to automatically store teh resulting access token.

Report · Apr 29, 2024

This worked for me, Thank you!

Report · May 15, 2024

Worked for me. Thanks

Report · May 11, 2023

The pre-sales staff supports you with integration-related inquiries while you utilise the Developer account.

When you need it, you can buy the service.

Thanks,

Report · May 11, 2023

some documentation seems to point to /public/oauth/v2/token, some seems to point to /oauth/v2/token . The stuff at https://opensource.adobe.com seems to be more accurate.

please fix your documentation.