I have the same problem as yours. I used to connect to CheckPoint VPN using snx inside a docker, but then it is useless due to passport integration.
Until now I also couldn't find the solution (using snx) yet.
But here is what I did to resolve the issue.
- Running a Linux server with GUI environment, I installed Windows OS in a KVM (virtual machine)
- Install latest version of CheckPoint app and configure the settings for using the passport authentication method
- Install ssh client inside the Windows and create a batch file to:
- detect VPN has been established or not
- use task scheduler to run SSH to create port forwarding between Windows localhost with remote server whenever the VPN was up
- Configure Windows firewall to allow port being accessed from Linux host (or you can disable the Windows firewall completely)
- And finally configure port forwarding (iptables, using Webmin) in the Linux host to allow other (Linux) users in the same network as the Linux server for accessing the remote node via Windows VM
Looks complicated but it works. No need for single Linux users to connect to CheckPoint individually. Just need a dedicated (Linux) server running Windows VM (or a Windows PC is also OK I think) to connect to CheckPoint VPN, and other Linux users just need to use it as the gateway (using the port forwarding).
Hope this can solve your issue. No need to migrate all Linux users to use Windows or Mac. But still need to put a budget and effort for preparing such gateway though. It's up to you which one is cheaper and efficient.