Pulse Secure HC reconects after reboot without turndown VPN session.

[SegEE]

Pulse Secure HC reconects after reboot without turndown VPN session.

Do you know how to disable this option?

[[email protected]]

Hi @SegEE ,

Can you please elaborate the issue? Are you implying that the Pulse Client connections are attempting to connect automatically after rebooting the system?

Thanks,

Ray.

[SegEE]

Hi [email protected] 

Whe you have a session, and then reboot the machine, at startup, if you have PS HC in the startup, it tryes to reconnect the last session. It remembers. Same occurs if start PS HC manually.

And also, if you let the machine suspended and you wake it up latter. It tryes to reconnect the las session of PS VPN. Always, into the MAX time out limit defined in the console.

Thanks in advance

[zanyterp]

What is "HC"?
Can you expand further on what you are reporting? are you using certificate authentication (only)?

[[email protected]]

Hi SegEE,

So you're telling that after rebooting/bringing up the machine from Hibernate state does always prompts you to continue the existing session instead of creating a new one???

Hmm...🤔 I believe, Hibernating the machine when connected to VPN, will not send any disconnect message to the VPN server (graceful) for disconnecting your session. In this case, your session will be alive on the VPN server and gets deleted only after reaching the configured session timeout value, which is the reason for getting session resumption prompt during the connection attempt.

@zanyterp: Do we see the same behaviour as hiberation, even the machine was rebooted during an active VPN session?

Thanks,
Ray.

[zanyterp]

yup, you are correct, [email protected]
the other option is that if certificate authentication is used, there is no prompt; the same is true when credentials are saved
if the message/issue that is being called out is related to the session being present, yes, the prompt will be shown unless a user logs out.
unfortunately, it is not clear what is happening

[SegEE]

Hello [email protected] ,

I dont know really, if it tries to save the last session or to create an other new session. It makes sense, as you was saying, when it hibernates and wakes up, it recovers the current session. I find dificult the same situation when rebooting your computer, but i dont really know.

We are not saving credentials and we dont use certification for authentication.

My CO is asking us if is possible to set any configuration in order not to reconnect or recover the connection. If the user let the computer alone, if he reboots or others situations, we want the user to reconnect consciously and intentionally. It is possible?

Thanks in advance.

[[email protected]]

Ok. So it seems that you are concerned about the Pulse Client's automatic connect behavior rather it's resuming the existing session. You would like to change the Pulse Client connection policy, so that the connection will get triggered only if the user manually clicks on connect, right?

How the connections are pushed/created on the Pulse Client?

Did you get those by launching the Pulse Client through a web browser session or was it created during the installation using deployment options like SCCM?

[zanyterp]

to change the automatic connect feature, please disable automatically connect on the connection set (both globally and in the specific connection)

[SegEE]

Thats the idea.

We usually trigger the client manually and them we connect using one of the connection butons depending of the profile we want.

Some times, some users use the web browser.

We deploy the client ussing a remote app. The 9.0r2 installer. I dont discard that some users did use the web browser to install. But it would be a residual number.

The point is, how to disable. Where we need to "touch".

Thanks!