• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Started getting 400 Bad Request attempting to refresh OAuth 2.0 Tokens

New Here ,
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:

screencap_adobe.PNG

Notes:

  1. The POST Url is the Shard that came back as the api_access_point, to which we appended /oauth/v2/refresh
  2. I double checked our Client ID and Client Secret, they are correct.  Also this is a certified app.
  3. 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

Views

150

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
no replies

Have something to add?

Join the conversation