Forum Discussion
Invalid issuer o signature error in SPO Provider-Hosted AddIns
Hello, I tried putting HostedAppHostNameOverride below Client Id and Client Secret tags in Web. Config file. But it didn't work as expected. List is still unable to trigger remote event receivers. Please advice.
Hello Rajat,
It did work for me, even for remote event receivers (at least the one being triggered when the add-in is being uninstalled).
The basic rule is to make sure that this value contains the text that is displayed to you in the error message "(...) is not the intended audience <important_text>". So you take the important_text value from your log message, strip if from the part before the "/" sign and the part after the "@" sign (see the content of TokenHelper.GetFormattedPrincipal method for details on what is going on there), and put it in the HostedAppHostNameOverride.
Also, as you've probably seen, the HostedAppHostNameOverride parameter can be a semicolon-separated-value, so you can put several values there.
Hope this helps.
Hello Slwomir
Thanks for Replying, I have two questions.
1) In order to deploy the apps on Azure and SharePoint Shall we need to have same login account for both ?
Let's say my Login account for SharePoint is - rajat.chauhan@xyztst.onmicrosoft.com
And My login Id for Azure is - rajat.chauhan@xyz365.onmicrosoft.com would it work ?
2) After adding the HostedAppHostNameOverride in application settings Do we need to generate new client ID and client secret to deploy apps ?
Thank you in advance
Hi,
I have no idea about the deployment thing. For me it seems that it does not matter who makes the deployment - but I guess you just need to check it.
As for the client id and secret - I didn't have to re-generate anything, luckily.