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
What Version of the library are you using?
Angular v.17
angular-auth-oidc-client version v16.0.1
Question
How can I get the latest information about the user? Without re-login?
We authenticate through Azure AD, utilizing refresh tokens, and so forth, and everything works fine except for one issue: I can't comprehend how to retrieve the updated user details in real-time if the username or surname has been changed.
For instance, in our application, we can modify our name in Azure AD, and upon change, Azure AD promptly returns the updated name. However, the angular-auth-oidc-client's userData observable continues to display the old data.
After successfully updating the information, I perform a forceRefreshSession, but it continues to return the old data, even with 5-second delay. If I attempt the action again, it returns the updated data. I don't understand this behavior.
What Version of the library are you using?
Angular v.17
angular-auth-oidc-client version v16.0.1
Question
How can I get the latest information about the user? Without re-login?
We authenticate through Azure AD, utilizing refresh tokens, and so forth, and everything works fine except for one issue: I can't comprehend how to retrieve the updated user details in real-time if the username or surname has been changed.
For instance, in our application, we can modify our name in Azure AD, and upon change, Azure AD promptly returns the updated name. However, the angular-auth-oidc-client's userData observable continues to display the old data.
After successfully updating the information, I perform a forceRefreshSession, but it continues to return the old data, even with 5-second delay. If I attempt the action again, it returns the updated data. I don't understand this behavior.
My configuration:
Thank you for your help!
The text was updated successfully, but these errors were encountered: