Users may encounter an error indicating that the client secret key for your Azure app is expired. This typically occurs when the secret key, reaches its designated expiration date.
When integrating with Azure services, you might encounter an error indicating that the client secret key for your Azure app is expired. This typically occurs when the secret key, reaches its designated expiration date.
⚠️THESE STEPS ARE BEST FOLLOWED BY AN IT OR TECHNICAL RESOURCE
Understanding the Error
The error message might look something like this (Client ID obscured for privacy):
Error while performing X Function: One or more errors occurred. (AADSTS7000222: The provided client secret keys for app 'XXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX' are expired...
Why Does This Happen?
Azure requires client secret keys for authentication purposes. These keys have a set expiry date to ensure security. Once expired, Azure no longer recognizes them, leading to authentication failures and errors in the Giving Data App.
How to Resolve the Error
Generate a New Client Secret
Sign in at Azure Portal and Navigate to 'App Registrations
In the left sidebar, click "Microsoft Entra ID"
-
Select App registrations >All Applications.
-
Choose the GivingData app with the expired key.
-
In the sidebar, create a new "Secret Key" by clicking "+ New client secret," add a description, and set an expiration (recommendation: 24 months).
- Copy/Save the New Secret: Once the secret is created, make sure to copy and save it somewhere secure. You won't be able to view the secret again after you leave the page.
Update Your System
-
Once the above steps are completed, open a Support Ticket and provide the new client secret in it so the GivingData Support team can update the system.
Troubleshooting
If you've followed these steps and find yourself still stuck, feel free to reach out to GivingData customer support for further assistance.