Adaptive Card: Validate User Identity Token

Vanny Pham

Hi, we have an adaptive card as an add-in button on the Constituent Page for non-privileged users to submit update to the Prospect module.

The add-in was working great; until I was testing something and decided to create a duplicate add-in (not 100% sure if this caused the issue).

Anyways, the Power Automate flow step to “Validate a user identity token” is now failing with this Error “Unhandled Operation ID-ValidateUserIdentityToken”. I have tried to delete the old application and created a new one, but I'm still having this issue. I have also tried to:

• (1) build a separate add-in card and
• (2) imported a similar flow package, and it's still not working.

I can't seem to find any solution elsewhere and I'm stuck on this error. Any support is greatly appreciated! Thank you in advance!

Alex Wong

@Vanny Pham
the Validate a user identity token 2 action is using an icon i cannot recognize.

The one to use is under the Blacbkaud SKY Add-ins aconnector, and the icon is circled below.

So I'm not sure which connector yours is falling under. if you go to edit mode, and then click on the ? icon

a help panel will show up on the right, then click on “Learn more”. that should take you to the reference documentation of the action, if you scroll to the top, you should see the connector in use.

Vanny Pham

@Alex Wong I think the icon must have been recently updated. I followed your step just to confirm and it is the Blackbaud Sky Add-in connector. I also didn't make any change to the flow from prior when it was working fine.

Erik Leaver

@Vanny Pham It looks like you might be in an area that was affected by an update to the SKY Add-in Connector which is causing the validate a user identity token to fail. We've remediated the issue and Microsoft is rolling out the update across regions. However we expect the update to take a few weeks as per Microsoft's deployment schedule. You can submit a ticket to Blackbaud support and reference defect 3264041.

Ben Wong

Hi @Vanny Pham, we heard reports of this bug and have released a fix in an update. Microsoft has told us that it will take 3-4 weeks before the fix will be deployed across regions. Unfortunately, there is no way for us to roll back the changes that introduced the bug. Sorry for the inconvenience.

Vanny Pham

@Erik Leaver Thank you so much for the update!

Vanny Pham

@Ben Wong Thank you!! Good to know that the fix is coming!

Austen Brown

@Ben Wong - For any existing flows already using this action, how will they be affected? Will they stop working?

Alex Wong

@Austen Brown
I have a handful of flows that does validate user identity token and they have been working just fine.

I think what Ben and Erik said is, a bug was introduced in the latest update made to Microsoft connector. So what I am understanding from the situation is (given none of my flow is failing) flow that was created previously to the update is ok. Flow that is created since the update has the error.

This will need Ben or Erik to confirm if true, but yea.. all my add-ins are working properly

Ben Wong

@Alex Wong @Austen Brown Microsoft have told us that the connector update with the bug was released in some regions. We think it may be in Asia and parts of Europe, but some Canadian customers have been impacted too. If you see the old Blackbaud SKY Add-ins logo, you should be unaffected.

Alex Wong

@Ben Wong
Thank you for the clarity

Austen Brown

@Ben Wong - Second Alex - thanks for the response!

Austen Brown

@Ben Wong - I built a new flow today that uses the ‘valid user identity token’ (the Sky Add-in connector has the old logo) and triggers from an add-in button. I'm running into an error (screenshot below) - not sure if this is the same issue Vanny reported. Weirdly, another flow in this environment also uses the ‘valid user identity token’ and ran this morning without any issues.

Any insight would be appreciated.

"The user identity token was missing or invalid, or the token has expired, or was issued to a different application or environment"

Ben Wong

@Austen Brown that doesn't appear to be related, since I can see that the request is getting through in order to get your error message. The user identity token can be invalid if it's expired (they only last for 5 mins), invalid (maybe malformed), missing, etc. You can also check the application ID that you are providing in the action to make sure that it's valid too e.g. is the correct app, valid form, etc.

If both of those values have been checked and you're still getting an error, I'd suggest creating a support ticket so that we can investigate further.

Thanks!

Austen Brown

@Ben Wong - Thanks for the response. I'll reach out to support.