I'm trying to connect to my Org's new vpn, but I'm having issues with the certificate. It is setup to use Microsoft azure AD (saml) for verification. Using the standard openconnect cli I can initiate a connection (although not complete the connection as I need the sso functionality) by providing the CA cert manually as per:
openconnect --cafile=ca.pem vpn.myorg.ac.uk
Using openconnect-sso, I know I need to be able to pass the CA cert for it to verify, but using what I believe should be the right syntax, I'm getting the error "certificate verify failed: unable to get local issuer certificate"
I'm trying to connect to my Org's new vpn, but I'm having issues with the certificate. It is setup to use Microsoft azure AD (saml) for verification. Using the standard openconnect cli I can initiate a connection (although not complete the connection as I need the sso functionality) by providing the CA cert manually as per:
openconnect --cafile=ca.pem vpn.myorg.ac.uk
Using openconnect-sso, I know I need to be able to pass the CA cert for it to verify, but using what I believe should be the right syntax, I'm getting the error "certificate verify failed: unable to get local issuer certificate"
openconnect-sso --server vpn.myorg.ac.uk -- --cafile=ca.pem
Any thoughts as to why it seems the ca cert isn't being passed to openconnect-sso?
I note that this issue did come up before (#48) but the resolution there was just to update openconnect-sso, I'm using the latest version 0.8.1