0
Started getting 400 Bad Request attempting to refresh OAuth 2.0 Tokens
New Here
,
/t5/adobe-acrobat-sign-discussions/started-getting-400-bad-request-attempting-to-refresh-oauth-2-0-tokens/td-p/13189401
Sep 09, 2022
Sep 09, 2022
Copy link to clipboard
Copied
We have Java code that would refresh OAuth 2.0 Code Flow Tokens based on this guide:
https://opensource.adobe.com/acrobat-sign/developer_guide/helloworld.html#refresh-token-request
After having this running fine, I did make changes to our Java code, and noticed that I can no longer refresh tokens.
I figured my changes broke our code. However, I stepped back and created a pure Postman Request and am getting a 400 Bad Request in Postman:
Notes:
- The POST Url is the Shard that came back as the api_access_point, to which we appended /oauth/v2/refresh
- I double checked our Client ID and Client Secret, they are correct. Also this is a certified app.
- The Test Refresh Token was obtained today
Are there issues with refreshing tokens on Adobe's side at the moment? Are others able to refresh tokens?
TOPICS
Adobe Sign forms
,
Login issues
,
Manage documents
,
Send documents
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting.
Learn more
Have something to add?
Join the conversation

