[GH-ISSUE #1203] Pulse Connect Secure VPN with Proxyman : working solution #1196

New issue

Open

opened 2026-03-03 19:49:13 +03:00 by kerem · 3 comments

kerem commented

2026-03-03 19:49:13 +03:00

Owner

Originally created by @florentmorin on GitHub (Apr 11, 2022).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1203

Originally assigned to: @NghiaTranUIT on GitHub.

I tried official process from Proxyman Documentation but it won't work.

So, here is my solution, with a very highly secured VPN.

First, you need to install OpenConnect.

brew install openconnect

You need to obtain installation path for openconnect.

whereis -b openconnect

After that, don't forget to edit /etc/sudoers

sudo visudo -f /etc/sudoers

Add this line and replace <openconnect-binary-path> with your binary path.

%admin  ALL=(ALL) NOPASSWD: <openconnect-binary-path>

Now, you can connect to your secured proxy using Juniper SSL / Pulse Connect Secure protocol.

 sudo openconnect --protocol nc -u <username> <proxy-url>

Once connected, launch Proxyman and it will work like a charm.

Originally created by @florentmorin on GitHub (Apr 11, 2022). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/1203 Originally assigned to: @NghiaTranUIT on GitHub. I tried official process from Proxyman Documentation but it won't work. So, here is my solution, with a very highly secured VPN. First, you need to install [OpenConnect](https://casper.infradead.org/openconnect/index.html). ```sh brew install openconnect ``` You need to obtain installation path for `openconnect`. ```sh whereis -b openconnect ``` After that, don't forget to edit `/etc/sudoers` ```sh sudo visudo -f /etc/sudoers ``` Add this line and replace `<openconnect-binary-path>` with your binary path. ``` %admin ALL=(ALL) NOPASSWD: <openconnect-binary-path> ``` Now, you can connect to your secured proxy using Juniper SSL / Pulse Connect Secure protocol. ```sh sudo openconnect --protocol nc -u <username> <proxy-url> ``` Once connected, launch Proxyman and it will work like a charm.

kerem commented

2026-03-03 19:49:14 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Apr 12, 2022):

Thanks @florentmorin. I added your suggestion to our official Doc at https://docs.proxyman.io/troubleshooting/proxyman-does-not-work-with-vpn-apps#4.-pulse-secure-and-global-protect-vpn

Thanks again for your contribution. I appreciate it 👍

@NghiaTranUIT commented on GitHub (Apr 12, 2022): Thanks @florentmorin. I added your suggestion to our official Doc at https://docs.proxyman.io/troubleshooting/proxyman-does-not-work-with-vpn-apps#4.-pulse-secure-and-global-protect-vpn Thanks again for your contribution. I appreciate it 👍

kerem commented

2026-03-03 19:49:14 +03:00

Author

Owner

@VaslD commented on GitHub (Apr 18, 2022):

I vote against editing sudoers, especially against putting it in a tutorial.

That step is useful (i.e. good to know) but not necessary. It also comes with security responsibilities (and, to most who needs a step-by-step VPN tutorial, security risks), because after editing sudoers, running openconnect still elevates to root but no longer requires admin password. That step should only be included in a section that has a big yellow exclamation mark at best; or removed altogether from the tutorial.

IMO a tutorial for a tool should not include a section that bypasses standard system security features, even if it's about using a built-in system tool to do so.

@VaslD commented on GitHub (Apr 18, 2022): I vote against editing `sudoers`, especially against putting it in a tutorial. That step is *useful* (i.e. good to know) but not **necessary**. It also comes with security responsibilities (and, to most who needs a step-by-step VPN tutorial, security risks), because after editing `sudoers`, running `openconnect` still elevates to root but no longer requires admin password. That step should only be included in a section that has a big yellow exclamation mark at best; or removed altogether from the tutorial. IMO a tutorial for a tool should not include a section that bypasses standard system security features, even if it's about using a built-in system tool to do so.

kerem commented

2026-03-03 19:49:14 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Apr 19, 2022):

Thanks. I will add a note to the Doc 👍

@NghiaTranUIT commented on GitHub (Apr 19, 2022): Thanks. I will add a note to the Doc 👍