Fixing AADSTS700082: refresh tokens expiring after 12 hours in Azure Entra External ID
The article discusses an issue with refresh tokens expiring after 12 hours in Azure Entra External ID, affecting user experience in a mobile app. The problem was traced to a configuration setting related to Sign-in Frequency rather than a bug in the refresh token system. The author provides insights into the symptoms, what was ruled out, and the eventual resolution of the issue.
- ▪Users of a mobile app experienced unexpected logouts due to refresh tokens expiring after 12 hours of inactivity.
- ▪The issue was linked to the Sign-in Frequency setting in Azure Entra External ID, not a bug in the refresh token mechanism.
- ▪The article outlines the troubleshooting process and confirms that the expected 90-day refresh token was being capped at 12 hours.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 1282259) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Sam Vanhoutte Posted on May 20 Fixing AADSTS700082: refresh tokens expiring after 12 hours in Azure Entra External ID #azure #oauth Fixing AADSTS700082: refresh tokens expiring after 12 hours in Azure Entra External ID At libelo we use Azure Entra External ID (CIAM) (Customer Identity and Access Management) as the identity provider for our React Native mobile app.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
