cancel
Showing results for 
Search instead for 
Did you mean: 

Azure SAML - Extend Session

DaveG
Contributor

Azure SAML - Extend Session

Hi all,

 

When connected via Azure authentication, if a user extends the session, they get a warning they already have a session open and if they want to continue. 

 

This is the same session, so I'm not sure allowing multiple session is the answer. Is this just how it works?

 

Using a Domain Controller as the authentication server doesn't cause this issue.

6 REPLIES 6
myPulseSec
New Contributor

Re: Azure SAML - Extend Session

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.

 

DaveG
Contributor

Re: Azure SAML - Extend Session

Thanks @myPulseSec , in a strange way, it's good to see that someone else has the same problem. 

zanyterp
Moderator

Re: Azure SAML - Extend Session

@ myPulseSec are you using the embedded browser or letting the authentication jump to IE?
zanyterp
Moderator

Re: Azure SAML - Extend Session

that should not be causing an issue. if you have not already done so, please open a case with our support team
can you confirm you are using the pulse embedded browser so that all authentication is staying within pulse?
DaveG
Contributor

Re: Azure SAML - Extend Session

Thanks @zanyterp , yes it seems to be the case that when extending a SAML connection using embedded brower, the connection is dropped first and the reconnected.

 

Will check with support.

zanyterp
Moderator

Re: Azure SAML - Extend Session

thank you for doing that; if the connection is being dropped and you are in the embedded browser, that is not expected