Invalid issuer o signature error in SPO Provider-Hosted AddIns affecting Remote Event Receivers

[jcgonzalezmartin]

Category

• Question
• Typo
• Bug
• Additional article idea

Expected or Desired Behavior

(Note: This issue was alrady reported here, but since It was unexpectedly closed, I'm re-opening it again as a new issue).We are having problems with SPO Provider-Hosted Add-Ins were we are using remote event receivers...all of these Add-Ins were working last week, but have stopped working Today. Could you please help us with identifying what's happening? We are seeing the problem in 4-5 tenants and with 2-3 different applications. I have attached a document with the troubleshooting we have done and also our findings. As you can imagine, it's quite urgent for us to get information and a workaround about how to fix it...we also opened a support case, but support folks told us that they don't provide help for this kind of issues. Thanks in advance!

Observed Behavior

Starting on the end of February, several of our customers are experiencing problems with SPO Provider-Hosted AddIns when getting the Context Token. The generic error we get is the following one: Invalid issuer o signature. Of course, we have already verified that this is not a problem with expired client secrets

Steps to Reproduce

I have included a document explaining all the troubleshooting we have done and also our findings

Invalid_isuer_or_signature_error_in_SPO.docx

Submission Guidelines

[VesaJuvonen]

Hi Juan Carlos, this is a hard one for us, as there's actually nothing we can do in the SharePoint side for this as the issue is in the Azure AD side. This means that we can't even route this properly internally for them as there are unfortunately no proper processes for that (yes - I know - there should be). That basically means that there's nothing we can, unfortunately, do from SharePoint side around this until we get the root cause fixed on the Azure side - as change is from their side.

In best case scenario we would get this reported through the Premier support targeted to Azure - as that's the most efficient way to get this resolved. The second alternative is to open it from support towards Azure, but wait times for that will be longer. As we can't really do anything for this in SharePoint side, we can certainly keep this issue open for now, if needed - but would ask to find alternative routes to get this reported using official channels towards Azure, so that the root cause would be fixed.

[jcgonzalezmartin]

Hi Vesa,
I really appreciate your message here and your very valuable advices. However, at this point we are in a dead road situation with this particular customer where we have not been able to fix the problems with the AddIns because any of the advices workarounds have worked. We already opened a support ticket in Azure, but Azure folks ended redirecting our request support to Office 365 and Office 365 folks have said that they cannot provide support to custom AddIns. Since my customer does not have a premier contract support, we do not have a solution path on that side either. Any other advice about how we could proceed here?
Thanks again for your time and commitment!

[andrewconnell]

it's been a while since this issue had any activity... if this is still an outstanding issue, can you please provide an update?

[msft-github-bot]

This issue has been automatically marked as stale because it has marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within next 7 days of this comment. Thank you for your contributions to SharePoint Developer activities.

[msft-github-bot]

Closing issue due no response from original author. If this issue is still occurring, please open a new issue with additional details. Notice that if you have included another related issue as additional comment on this, please open that also as separate issue, so that we can track it independently.

[msft-github-bot]

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues