After SAML authentication getting: Matching client config not found

[mehrdadziaei]

We have two global protect server, one of them is configured for SAML authentication.

When using gpclient, I can successfully login with username/password to the one configured against AD LDAP.
But when trying to login to GP server configured with SAML, I do get the popup browser and SAML authentication goes through fine, but it does not connect to GP, I get "Matching client config not found"
I can connect with the same user from a Windows client, so I know the user has access to GP.

Here is the log after SAML authentication is done:
2022-01-18 13:33:48.799 INFO [35451] [GPClient::onVPNLogAvailable@489] Start process with arugments: --protocol=gp -u [email protected] --cookie-on-stdin vpn.example.com
2022-01-18 13:33:48.799 INFO [35451] [GPClient::onVPNLogAvailable@489] Openconnect started successfully, PID=35532
2022-01-18 13:33:48.799 INFO [35451] [GPClient::onVPNLogAvailable@489] POST https://vpn.example.com/ssl-vpn/getconfig.esp

2022-01-18 13:33:48.858 INFO [35451] [GPClient::onVPNLogAvailable@489] Connected to 12.34.56.78:443

2022-01-18 13:33:49.001 INFO [35451] [GPClient::onVPNLogAvailable@489] SSL negotiation with vpn.example.com

2022-01-18 13:33:49.052 INFO [35451] [GPClient::onVPNLogAvailable@489] Connected to HTTPS on vpn.example.com with ciphersuite (TLS1.2)-(ECDHE-SECP256R1)-(RSA-SHA256)-(AES-256-GCM)

2022-01-18 13:33:49.089 INFO [35451] [GPClient::onVPNLogAvailable@489] Matching client config not found
Creating SSL connection failed

2022-01-18 13:33:49.094 INFO [35451] [GPClient::onVPNLogAvailable@489] Openconnect process exited with code 1 and exit status NormalExit

Is this a misconfiguration or a bug?

Thanks,

[tyler-bixal]

#96 works for me to get around this.

[gleissonneves]

how did you see these logs?