Issue with generating new client secret for Azure hosted sharepoint App

%3CLINGO-SUB%20id%3D%22lingo-sub-321591%22%20slang%3D%22en-US%22%3EIssue%20with%20generating%20new%20client%20secret%20for%20Azure%20hosted%20sharepoint%20App%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-321591%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EHello%2C%20We%20are%20having%20issues%20on%20updating%20an%20expired%20client%20secret%20for%20a%20Azure%20hosted%20sharepoint%20add%20on.%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EWe%20have%20followed%20below%20guide%20to%20renew%20the%20clientsecret%20and%20have%20done%20so%20in%20the%20past%20using%20the%20same%20method%20%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsharepoint%2Fdev%2Fsp-add-ins%2Freplace-an-expiring-client-secret-in-a-sharepoint-add-in%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsharepoint%2Fdev%2Fsp-add-ins%2Freplace-an-expiring-client-secret-in-a-sharepoint-add-in%3C%2FA%3E%20But%20now%20we%20get%20an%20error%20saying%20%22Invalid%20issuer%20or%20signature.%22%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAnother%20possible%20solution%20we%20have%20tried%20was%20using%20this%20page%20to%20create%20the%20new%20service%20principle%20(as%20other%20online%20sources%20reported%20this%20might%20solve%20our%20issue).%20But%20the%20page%20always%20gives%20us%20a%20%22Oops%20something%20went%20wrong%20message%22%20%3A%20%22https%3A%2F%2FOUR%20SHARPOINT%20SITE%2F_layouts%2F15%2FAppRegNew.aspx%22%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EWe%20have%20also%20used%20the%26nbsp%3BRemove-MsolServicePrincipalCredential%20command%2C%20and%20removed%20all%20the%20keys%20for%20this%20clientID%20and%20generated%20a%20new%20on%20afterwards%2C%20with%20no%20success%20either.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20last%20suggestion%20I%20found%20online%20was%20to%20add%26nbsp%3B%3CADD%20key%3D%22%26quot%3BHostedAppHostNameOverride%26quot%3B%22%20value%3D%22%26quot%3Bxxxx.azurewebsites.net%26quot%3B%22%3E%3C%2FADD%3E%20to%20our%20web.config%20file.%20But%20this%20also%20does%20not%20help.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20had%20created%20a%20ticket%20with%20Microsoft%20and%20they%20advised%20me%20to%20create%20a%20post%20here.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EDoes%20anybody%20have%20any%20ideas%20we%20could%20try%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EKind%20Regards%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-324235%22%20slang%3D%22en-US%22%3ERe%3A%20Issue%20with%20generating%20new%20client%20secret%20for%20Azure%20hosted%20sharepoint%20App%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-324235%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20Thank%20you%20for%20the%20tip.%20But%20we%20allready%20waited%2048h%20between%20friday%20and%20monday%2C%20and%20still%20no%20success.%3C%2FP%3E%3CP%3EOn%20monday%20we%20deleted%20everything%20and%20tried%20again%20with%20%22assistance%22%20from%20the%20O365%20support%20team%2C%20and%20now%2048h%20later%20it%20still%20does%20not%20work...%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-321683%22%20slang%3D%22en-US%22%3ERe%3A%20Issue%20with%20generating%20new%20client%20secret%20for%20Azure%20hosted%20sharepoint%20App%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-321683%22%20slang%3D%22en-US%22%3E%3CP%20style%3D%22text-align%3A%20left%3B%22%3EI've%20seen%20the%20registrations%20take%20upwards%20of%2024%20hours%20from%20the%20creation.%20So%20when%20you%20generate%20your%20new%20secret%2C%20and%20update%20your%20web.config%20for%20application%2C%20it%20will%20take%2024%20hours%20before%20it%20can%20be%20used.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hello, We are having issues on updating an expired client secret for a Azure hosted sharepoint add on.

 

We have followed below guide to renew the clientsecret and have done so in the past using the same method : https://docs.microsoft.com/en-us/sharepoint/dev/sp-add-ins/replace-an-expiring-client-secret-in-a-sh... But now we get an error saying "Invalid issuer or signature."

 

Another possible solution we have tried was using this page to create the new service principle (as other online sources reported this might solve our issue). But the page always gives us a "Oops something went wrong message" : "https://OUR SHARPOINT SITE/_layouts/15/AppRegNew.aspx" 

 

We have also used the Remove-MsolServicePrincipalCredential command, and removed all the keys for this clientID and generated a new on afterwards, with no success either.

 

The last suggestion I found online was to add <add key="HostedAppHostNameOverride" value="xxxx.azurewebsites.net" /> to our web.config file. But this also does not help.

 

I had created a ticket with Microsoft and they advised me to create a post here.

 

Does anybody have any ideas we could try?

 

Kind Regards

 

 

 

2 Replies

I've seen the registrations take upwards of 24 hours from the creation. So when you generate your new secret, and update your web.config for application, it will take 24 hours before it can be used. 

Hi, Thank you for the tip. But we allready waited 48h between friday and monday, and still no success.

On monday we deleted everything and tried again with "assistance" from the O365 support team, and now 48h later it still does not work...