I've run into an issue where all my pipelines in Azure DevOps suddenly stopped working. After some investigation, I discovered that several service principal secrets had expired. I regenerated these secrets and updated the service connection details, but unfortunately, the problem persists. The error message I keep receiving includes: 'AADSTS7000222: The provided client secret keys for app are expired.' It advises me to visit the Azure portal to create new keys for my app or consider using certificate credentials for better security. Importantly, no changes have been made to the repo code, so I'm not sure what else could be causing this issue.
4 Answers
Switching to workload identity credentials might be a good long-term solution. They tend to be more secure and don't have the expiration issue like secrets do, but you'd need to ensure your setup supports it.
For anyone else facing similar issues, if you’re using agents, try rebooting them too. Sometimes that can help clear up any lingering issues.
It looks like the main issue here is that the client secret keys for your app have expired. Client secrets can become invalid over time, and you need to renew them and update the affected services. No code changes should have caused this, it's just a maintenance task you need to handle every now and then.
Good to hear the issue is resolved! Just a note for the future—make sure there aren't any similar service connection names, as that can lead to confusion like what you experienced. And consider looking into workload identity for added security.
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically