Safeguarding your Appspace Intranet is essential, and managing the Client Secret is crucial for maintaining secure communication between Appspace Intranet and Microsoft Azure, minimizing the risk of service disruptions.
This article provides Administrators with an outline for checking and updating the client secret key for the Appspace Intranet Add-in by running specific scripts and adjusting Azure App Service settings or the Azure Key Vault, ensuring the add-in’s continued functionality.
Prerequisites
- The Global Administrator user role with Windows Server Administrator permissions.
Check an Expiring Client Secret Key
To ensure your Add-in remains functional, you can check the client secret expiration date by running the following script from the installation folder:
./beezy-GetAddinExpirationDate.ps1
After running the script, you’ll be prompted to enter your O365 tenant credentials. The output will display the Appspace Intranet Add-in details, including the Principal Name (“Beezy”) and the EndDate, which indicates the expiration date of the Add-in Client Secret.
Replace an Expiring Client Secret Key
To replace an expiring client secret, you can run the following script from the installation folder:
./beezy-ReplaceAddinExpiringClientSecret.ps1
After running the script, you’ll be prompted to enter your O365 tenant credentials.
Save the client secret generated by the script. In your Azure App Service that hosts the Appspace Intranet, navigate to Application settings > App settings.
- Add a key named SecondaryClientSecret with the value of your old client secret.
- Update the ClientSecret key with the newly generated client secret.
For more details, refer to the source: MSDN Documentation.
As mentioned in the previous guide, please allow at least 24 hours for the new ClientSecret to propagate to SharePoint Online (SPO).