Power Automate Base64 Encoded Private Key

[Trigyn29817409ue1g]

Not able to find Power Automate Base64 Encoded Private Key 

Where to look at?

Thanks

ananda

[Raymond Camden · Accepted solution]

It would be in the credentials you downloaded. 

[Wavey05]

Hi I have the same problem and the Base64 Encoded Private Key is not in any of the downloads I have or on the website anywhere that I can see. Thanks for any help you can provide. 

[Raymond Camden]

Do you have the zip of the credentials you got when you signed up?

[Will310416659uh7]

Yes I do and it is not in any of the files that I have downloaded. 

[Lonny32520875einb]

I have the same issues.  I have all the required credential pieces except for the Base64 Endoced Private Key.  Not in the download nor anywhere in the Console.

[Raymond Camden]

It should have been in the original download, but you can generate a new key in the console.

[Lonny32520875einb]

The only thing that can be created is an access token.  I tried this but it won't allow me to authenticate.  keeps getting an error when creating the conneciton in Power Automate stating TEst Connection failed.  Details:  Private key file could not be parsed. 

[Raymond Camden]

When you are in the console, do you see the option to make JWT-based credentials? You will get a warning about it being deprecated, but it will include a key.

[Lonny32520875einb]

I did not have that option.  I creaed a new project using the JWT option a while ago, but it was missing the other credentials to enter so i thought that was the wrong route.  Just now I updated that project to a OATH project and then both options were available.  ust missed one step.

[jad3253347454o0]

Hello @Raymond Camden ,

I have the same issue as @Lonny32520875einb I am not able to find the Base 64 encoded private key.
I tried to use the below:

Any idea what will be the resolution?

[Raymond Camden]

Make a new key in the developer console as I suggested above.

[jasper372299367z7d]

hello, i am having the same issue, went through all the forums and found that above mentioned solution does not work. 

So asking again this community - where the heck can we find the Base64 Encoded Private Key, its not mentioned anywhere in the downloaded files or on the adobe website. 

would be great if someone could help who already solved this issue - its about connecting microsoft automate with adobe pdf services. Thanks!

[Raymond Camden]

There is no key anymore, only a client ID and client secret. When you set your connection up in PA, you will only be asked for those two values.

[jasper372299367z7d]

ah, great. I deleted the old word to pdf connector in flow and replaced it with the same "new" version. 

succesfully created the new adobe credentials accordingly, and when saving the flow the connection seems to be established. 

At least i can see on adobes side that the key has been used. 

However,  the flow does not run and tells me "not authorised to perform this operation". No idea why. 

Below is the raw output code, maybe someone can give me a hint in which direction to look:

{

    "statusCode": 401,

    "headers": {

        "Cache-Control": "no-store, must-revalidate, no-cache",

        "Transfer-Encoding": "chunked",

        "X-Request-ID": "7ouzbIKgUagBojxgsI7sTstQ2pFCoc5p",

        "Pragma": "no-cache",

        "X-Content-Type-Options": "nosniff",

        "Strict-Transport-Security": "max-age=31536000; includeSubdomains",

        "x-robots-tag": "noindex,nofollow",

        "Vary": "accept-encoding",

        "Timing-Allow-Origin": "*",

        "x-ms-apihub-cached-response": "false",

        "x-ms-apihub-obo": "false",

        "Date": "Wed, 08 May 2024 03:03:50 GMT",

        "Content-Type": "application/json",

        "Expires": "Thu, 01 Dec 1994 16:00:00 GMT",

        "Content-Length": "102"

    },

    "body": {

        "error": {

            "code": "401",

            "message": "Not authorised to perform the operation."

        }

    }

}