Hi @hawthorne91
Thank you for posting this in Microsoft Q&A.
I understand your concern regarding the Refresh Token Lifetime Issue, Expiring in 1 Day Instead of 7 days.
The maximum time period before which a refresh token can be used to acquire a new access token, if your application had been granted the offline_access
scope. The default is 14 days. The minimum (inclusive) is one day. The maximum (inclusive) 90 days.
I've set the Refresh Token Sliding Window Lifetime to "No expiry." Does this mean that the token will be refreshed each time it's used?
The refresh token sliding window type. Bounded
indicates that the refresh token can be extended as specified in the Lifetime length (days). No expiry
indicates that the refresh token sliding window lifetime never expires.
Could someone explain why the refresh token is expiring in just one day instead of the 7 days I've configured?
Single-page applications utilizing the authorization code flow with PKCE are always subject to a refresh token lifetime of 24 hours, whereas mobile, desktop, and other web applications are not constrained by this limitation.
The refresh_token_expires in one day, due to the use of the PKCE authentication flow to obtain the access token, even if the Refresh Token Sliding Window is configured.
For more information: Configure tokens in Azure Active Directory B2C
Hope this helps. Do let us know if you any further queries.
Thanks,
Navya.
If this answers your query, do click Accept Answer
and Yes
for was this answer helpful. And, if you have any further query do let us know.