Skip to main content
L
LC26326529l959
Participant
May 10, 2023
Answered

Updating Adobe Power Automate connector from JWT to OAuth2.0 credentials

  • May 10, 2023
  • 1 reply
  • 1916 views

Hi all,

I'd like to preface this post by saying I am not a developer, just someone who likes to use tools available to make work asier. I've created multiple Power Automate flows using the Acrobat API connector, and am now getting a lot of emaile about creating new credentials with OAuth2.0 or my flows will break (albeit not until Jan 2025). 

 

I've gotten as far as creating the OAuth credential, but not sure how to complete the migration away from the old JWT.

 

 

When I click on the OAuth Server-to-server credential, I see the following fields that I can then copy and paste into the Adobe PDF Services Power Automate connector:

 

 

 

 

My question is this: What do I put in the Base64 encoded private key? In the JWT credentials, there was an option to generate a public/private access key, that downloaded a zip file containing the private key that I could then paste in there.

 

I've clicked on the OAuth generate access token and entered that into the box, but got an error message. 

 

I should also note that I am no longer using the free version of the PDF Services API, and am paying per API call through AWS Marketplace subscription. I recently gotten the below email. I assume it must have to do with the JWT credentials they're phasing out, but seein gas how I'm getting billed through AWS, how can they no longer support it? Prob a question from AWS, but thought it might be relevant to the above issue.

 

    This topic has been closed for replies.
    Correct answer Raymond Camden

    Hi, so you've got two things going on:

     

    1) We (Adobe as a whole, not just Acrobat Services), launched a new authentication system. However, the various SDKs and implementations like PA have *not* been updated yet. For now, just sit tight. If for some reason you are using the REST APIs outside of PA, you can use the new credentials, but PA and SDK users need to just wait for now.

     

    2) Yes, we no longer support AWS as a way to pay. See this post for info: https://community.adobe.com/t5/acrobat-services-api-discussions/adobe-pdf-services-api-availability-on-amazon-aws/td-p/13782839

    1 reply

    Raymond Camden
    Community Manager
    Raymond CamdenCommunity ManagerCorrect answer
    Community Manager
    May 16, 2023

    Hi, so you've got two things going on:

     

    1) We (Adobe as a whole, not just Acrobat Services), launched a new authentication system. However, the various SDKs and implementations like PA have *not* been updated yet. For now, just sit tight. If for some reason you are using the REST APIs outside of PA, you can use the new credentials, but PA and SDK users need to just wait for now.

     

    2) Yes, we no longer support AWS as a way to pay. See this post for info: https://community.adobe.com/t5/acrobat-services-api-discussions/adobe-pdf-services-api-availability-on-amazon-aws/td-p/13782839

      J
      Jörg22808859zij2
      Participant
      July 6, 2023

      Are you (Adobe) serious about this!? You shut down the old API before the transition to the new API is complete?

      I'm paying Adobe a monthly subscription for using their services and now the Power Automate flows I need for business stop working!

      It's been almost two months since this post has been made, how much longer should we wait for a solution!?

      V
      Villy30517074f00t
      Participant
      July 6, 2023

      Hi Jörg22808859zij2,

       

      I was in this predicament 24 hours ago however I found a solution to it (albeit temporary). I created a new project in the Dev Console and added the PDF Services API with a new step in the creation process. When creating the credentials, I selected the deprecated JWT method and ignored the nag messages. I then followed the prompts to create a public & private key by stepping through this process. At the end I was presented with all the information that I needed making note that the Base64 key was the private.key file contained in the zip file which was downloaded during the key creation process. When adding the Adobe PDF Services connector in PA, be sure to copy&paste the entire key including the <begin> and <end> tags in the key text.

       

      You may need to go into your PA flows and with each adobe component (hit the 3 dots) and select the new connector to realign the PDF service to the newly created connector.

       

      I am unsure if this will help you but this is how I resolved getting my flows back onstream.

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices