Error accessing server with SAML. Signature signing problem

[jose867]

Hello! Great software, it has changed my life since I discovered it.

It has always been a Greek epic to connect to my company's Globalprotect server from Linux.

The thing is that everything has been working perfectly for the last few months, but now I find this:

org.opensaml.saml.common.SAMLException: No signature signing parameter is available

Has anyone found it? Thank you!

[yuezk]

org.opensaml.saml.common.SAMLException: No signature signing parameter is available

Is the log collected from the VPN server side?

[yuezk]

And is the client broken now?

[jose867]

Yes... server side log...

It's funny that I can connect after several attempts. Using the "default browser" option has solved most of the problems I have always had. I understand that the server has qualms with something that is not its official client.

[jose867]

I finally can connect... after a couple of tries. Taking into account that I have just launched a command, copied a cookie, pasted a command with a cookie... and waited for the correct connection, keeping the terminal always open. A proposal, I always have to modify the routing tables, eliminate the one that creates the connection so that all traffic goes through the VPN and route only the IP range that interests me... Networkmanager allows modifying the routes imposed by the server , For example. It worked very well until SAML was implemented... I could never use it to connect again

[yuezk]

The client delegates the SAML authentication to the external browser/webview. and intercept the cookies/tokens to connect to the VPN server. It does no special handling for the SAML authentication. I assume the error message on the server side may not be specific to this client.

Networkmanager allows modifying the routes imposed by the server

I'm interested in supporting this