Copy link to clipboard
I reached the free trial quota for the integration which was 1000 uses. I just subscribed with a 5 cent per use charge since I don't have enough time to talk to a sales rep about increasing the quota.
I want to integrate PDF tools with microsoft power automate. I have all credentials such as the client id, client secret, technical account, etc, BUT I do not have the Base-64 encoded Private Key, I NEED this to integrate.
I can copy and past all these things to microsoft power automate.... BUT NO Base 64 encrypted private key. I have a downloaded zip with some info, but it the info in the downloaded zip does not match the info presented on my main projects screen for the specific API.
Copy link to clipboard
In the Manage Connections settings of Power Automate, edit your connection.
When the dialog first opens, the Client Secret and Base64 Encoded Private Key will be empty.
Click in one of the fields. You'll be prompted to enter your password and then both fields will populate.
Click into a field again to expose the actual value.
If you use this URL to create your PDF Tools key using this link, it will provide your key in Base64. Otherwise, if you create it from Adobe.io, you will have to encode your private key you downloaded and convert it to base64.
Hi, I am experiencing similar issues having run a trial of the PDF Tools (which worked just fine for my use case).
After the trial I subscribed to the PDF Tools on AWS and followed the link through to Adobe to create my new project. I had a "system error" display when adding the project (which was consistent for a couple of days and multiple restarts) but it did create them as they show on the Adobe Console.
When I go back into Power Automate and Edit the Connector, I dont get the password popup but can add the Secret and Private Key manually, which gets authenticated. But then the Flows using the Connector timesout with (unsurprisngly):
Either Quota for this operation is not available or Free trial quota is exhausted. Please visit (www.adobe.com/go/pdftoolsapi_home) to start using free trial quota or (www.adobe.com/go/pdftoolsapi_err_quota) to upgrade to paid credentials.
So seems my AWS subscription is not tied to the Adobe Project, any way to force that connection?
I have the same issue, I can not get AWS subscription to connect to the Power Automate API project. I have ben chatting with Adobe support and AWS support, they are just reffering to eachother.
I tried using the private key as per answer below, via "normal" API key cridentials but I fails. Im stuck??
Adobe support had a look at this for me. The fix was to cancel teh AWS subscription, create a new one and try again. Worked 🙂
Where do the credentials come from? I don't understand how to create the credentials for a paid subscription. As far as I can tell, only trial subscription credentials can be created at adobe.io. What am I missing?
Is it really as simple as "cancel AWS subscription and create a new one"???
Update: yes it was really that simple. I did mess around with the AWS console and changed or enabled some settings in there... Not sure if any of that was necessary. There were some semi-obvious cues in the AWS Manage Subscriptions and License Manager sections that I followed. I basically just did whatever the prompts at the top of the page told me to do. Anyway, I don't believe that stuff was the problem. I cancelled the SaaS subscription for Adobe PDF Tools API and then made a new one and it worked right away.
Now, lets see if it keeps working after the 500-document quota that it gave me. AWS has my billing info, so I'm assuming we'll start generating a bill after we use up this quota. Wish me luck!
Copy link to clipboard
When you create credentials, it will download a ZIP file with the private.key and the pdftools-api-credentials.json files. If you open both of those in your text editor, you will see the values you need to enter into Power Automate. If you open the Private Key file, copy the entire contents of that file into the Private Key field. That should allow you to authenticate.
Thanks Ben. It seems to authenticate ok, just when the Flow runs it times-out. Almost like the link to the paid AWS subscription is broken. Setup with another trial to check it was not something in Flow, new trial worked fine.
Might go back to drawing board and register for a new AWS subscription and try again.
Shame as the process works very well.
Following your insctructions I get this: