Thank you for your answer.  No, when using Active Directory for example I do not get the warning that there is already an existing session for that user. This works as expected. Of course, the user needs to reauthenticate against Active Directory as well when extending the session, but as you have mentioned the tunnel does not get dropped.    The re-authentication in general is ok when extending the session. When using SAML Authentication the user needs to reauthenticate as well. All good so far. However, after successfully authenticating, the Pulse Secure somehow cannot match the existing session, which leads to the mentioned warning message. ... View more

Hey,  I have experienced exactly the same... Authenticating against Azure AD to extend the existing session always leads to a warning, that there is already an existing session. If you select the option to "keep the existing session", the session gets closed (no active session for the user anymore on the Pulse Secure "active user" tab).    If I select "Connect" to close the existing session and start a new one I will obviously be requested to sign in again against Azure AD.    Would be great if anyone has a solution for that.  Thank you.   ... View more

Hey r@yElr3y,    do you know if this should have been resolved already? I have tested it and saw the same behavior on v9.1R10.  If I disable the user session warning, I still experience the behavior that a new session is created and session related applications are disconnected, due to the process of reconnecting.   Basically the user session warning popup would not be the problem, as there is the option to keep the old session, but if I do so, the session still gets disconnected on the Pulse Connect Secure.    Thank you. ... View more