Failed to validate token Timebomb

(2) Share

Report

Posted on by abc 123

784 Moderator

For the love of all that is Holy, what is this timebomb that Microsoft has detonated in my Flow?

Error from token exchange: Bad Key authorization token.

Token must be a valid JWT signed with HS256
Failed to validate token: IDX10249: X509SecurityKey validation failed. The associated certificate has expired. ValidTo (UTC): '5/2/2024 11:59:59 PM', Current time (UTC): '5/5/2024 1:52:21 PM'.

Action: Send HTTP request to SharePoint

Method: POST

Body:

{
"__metadata": { "type": "SP.Data.WfAutoPopListItem"},
"StartAutoPop" : "false", (A Yes/No column)
"Status" : "Running", (A Choice column)
"Completed" : "2024-05-05T13:56:47.2540904Z", (A Date/Time column)
"wfErrorLog" : "" (A Single Line of Text column)
}

Results:

{

"status": 400,

"source": "https://power-te-westus-1.azurewebsites.net:443/tokens/msmanaged-na/sharepointonline/20ae94b828064029931d8e785dc6887f/exchange",

"message": "Error from token exchange: Bad Key authorization token. Token must be a valid JWT signed with HS256\r\nFailed to validate token: IDX10249: X509SecurityKey validation failed. The associated certificate has expired. ValidTo (UTC): '5/2/2024 11:59:59 PM', Current time (UTC): '5/5/2024 1:52:21 PM'.\r\n"

}

Categories:

General topics

I have the same question (0)

All responses (5)

Answers (2)

Nived_Nambiar 18,129 Super User 2025 Season 2 on at

Like (1)

Report

Hi @GDSI

Just to confirm - are you updating column values in your sharepoint list ?

Thanks & Regards,
Nived N 🚀

LinkedIn: Nived N's LinkedIn
YouTube: Nived N's YouTube Channel
Blog: Nived Nambiar's Blogs

🔍 Found my answer helpful? Please consider marking it as the solution!
Your appreciation keeps me motivated. Thank you! 🙌

Was this reply helpful? Yes No
Verified answer

abc 123 784 Moderator on at

Like (2)

Report

It appears that the connection reference has "expired".
I've created a new one and replaced the timebomb.

Why does it do this?

Was this reply helpful? Yes No
Verified answer

abc 123 784 Moderator on at

Like (2)

Report

A Microsoft support tech had this to offer:
"The connection key for open API flows expires every 390 days, and we do not automatically refresh the connection keys. Expired connection keys cause the flow run to fail."

There is no warning, no way to see how soon something is going to expire, nor a notification that it has expired. This time bomb is absolutely unacceptable and unprofessional. But I'm not going to ask shocked or surprised and the lack of caring from the Interns at Microsoft. Shame on them, nonetheless.

Was this reply helpful? Yes No
automateUser 4 on at

Like (1)

Report

I've notice this in our environment and it can be a real problem when there are multiple connector connections under the same account and they expire at different times. I wonder if this certificate expiration tied to the prompt that pops up when visiting the power automate "My flows" page:

"{x number} of your connections need to be reauthenticated to avoid the following flows from failing. The most common cause is a password change or policy update from your org"

note: not sure how the above msg is detecting the change(s)...since there has not been any password change and any obvious policy update -- so what constitutes a policy update related for this prompt?

Depending on where the token expiration happens, it could fail at the beginning of the trigger action, in the middle, or the end of the power automate actions.

Has anyone have any luck discovering other ways to mitigate this issue? or at least discovering when this expiration will happen for a flow connection?

Was this reply helpful? Yes No
EH-07050809-0 2 on at

Like (0)

Report
Just got this error. To fix it, I followed these steps:

In "My flows", select the broken flow.

Select 'Edit'.

Open the broken step - just doing this seems to recreate the connection.

Save the flow.

Run the flow again.

Good luck 😊

And thanks to folks on this thread for your help. The help within the app was pretty poor - the instructions didn't match the elements I could see on my screen.

Was this reply helpful? Yes No