-
-
Notifications
You must be signed in to change notification settings - Fork 140
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
Matching client config not found #96
Comments
@aallrd Try to fill the |
A similar issue was reported in #54. You can keep the And a related issue in OpenConnect is https://gitlab.com/openconnect/openconnect/-/issues/246 |
You can try to spoof the client, see https://gitlab.com/openconnect/openconnect/-/issues/246#note_582114977 |
Reading some related issues on the openconnect project and playing also with https://github.com/dlenski/gp-saml-gui I found that the issue we are actually not using GlobalProtect as a VPN but as a user-id agent. |
Hello,
Thank you for this application that is already a lot nicer than the official Palo Alto GlobalProtect client on Linux.
I am trying to connect to our GlobalProtect gateway using a SAML authentication but so far I am unable to make it work.
I have installed the client on my Fedora Workstation 34 using the project's documentation and it worked without a glitch.
The first time I clicked on Connect I had my company authentication webpage prompting me for my username/password but then it stayed in status Not Connected.
Clicking on Connect after that shows Authenticating... then it brings out a pop-up that closes very fast and Not Connected again.
Here are the logs (redacted with GATEWAY, USERNAME and COMPANY):
It seems that the SAML authentication works fine but it fails right after that.
I have noticed that the
-u
argument is not set in the finalopenconnect
command.I am able to reproduce the same issue by calling directly
openconnect
(and filling the missing username):I think we are using a MFA authentication process on our Windows laptops.
Do you have any idea what the issue could be?
The text was updated successfully, but these errors were encountered: