You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Access token is not getting refreshed when user is already logged in.
The processLogin() refreshes the IdToken when getAccount() is successful but does not perform a refresh of access token before triggering LoginSuccess event. This causes any subsequent API calls that requires the access token to fail without a manual user login process. Is it intentional to not renew the access token?
Expected behavior
when token is renewed, both id token and access token should be renewed before LoginSuccess event is triggered. If one of them fails, login should be considered a failure.
Desktop (please complete the following information):
OS: macOS
Browser: Chrome
Version 84.0.4147.105
The text was updated successfully, but these errors were encountered:
Library versions
react-aad-msal
: 2.3.5msal
: 1.3.2Describe the bug
Access token is not getting refreshed when user is already logged in.
The processLogin() refreshes the IdToken when getAccount() is successful but does not perform a refresh of access token before triggering LoginSuccess event. This causes any subsequent API calls that requires the access token to fail without a manual user login process. Is it intentional to not renew the access token?
react-aad/packages/react-aad-msal/src/MsalAuthProvider.ts
Line 333 in a7205ef
Expected behavior
when token is renewed, both id token and access token should be renewed before LoginSuccess event is triggered. If one of them fails, login should be considered a failure.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: