Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Need to re-authenticate every time I reconnect to the VPN on a CLI-only server #463

Closed
dingsheng-ong opened this issue Jan 15, 2025 · 2 comments

Comments

@dingsheng-ong
Copy link

I’ve managed to connect to my VPN on a CLI-only server, but the problem is that I have to authenticate every time I reconnect to the VPN. Here’s the process I’ve been following:

  1. On the server, I run gpclient connect ..., which starts a local server accessible at 127.0.0.1:<port1>/<hash> and listens on another port <port2> for authentication data.
  2. On my PC (with a GUI), I use ssh -L to bind <port1> to port 80 on my PC. I then complete the authentication process using a browser on my PC.
  3. After step 2, I get the globalprotectcallback: <base64-string>. I return to the server and send the callback string using netcat: echo -n "globalprotectcallback: <base64-string>" | nc 127.0.0.1 <port2>

This method works, and I can connect to the VPN. However, every time I disconnect and reconnect starting from step 1, I have to repeat the entire authentication process. On the other hand, the GUI version of the VPN client automatically saves the authentication data, so it connects seamlessly without requiring me to authenticate again.

Q: Is there a way to save the authentication data or session cookies on the CLI-only server so that I don’t have to go through the authentication process every time I reconnect to the VPN?

@yuezk
Copy link
Owner

yuezk commented Jan 21, 2025

Currently, there is no way to save the session cookies for the CLI.

@dingsheng-ong
Copy link
Author

I guess I’ll figure out another way to do that. Thanks for the response anyway, cheers! :-)

@dingsheng-ong dingsheng-ong closed this as not planned Won't fix, can't repro, duplicate, stale Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants