Azure AD: Best Practices on session timeout / token invalidation
Dear all,
we are working together with a software provider that provides a password manager solution, based on a classic client-server architecture. The users authenticate via the client through Azure AD in order to access the server.
We do have a corporate security requirement that any idle session (5 minutes) shall be force closed, which also applies to said application.
However, given that we receive the session token from Azure AD, the timeout settings from AAD apply (1 hour or more), which violates the requirement. Speaking to the vendor, he says that they should not control the session timeout via the client. Relaying on the AAD setting would be SSO best practice and this is how all other OAuth2/OIDC clients work. Instead, they refer to the AAD to decrease the token's life time.
As I am not an expert in this field, could you please comment on this?
Thanks in advance,
André
Microsoft Entra ID
1 answer
Sort by: Most helpful
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more