-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add multi-certificate authentication to client #60
Conversation
Test Result🙌 254 Tests pass Test Details🟢 TestAddrMonStartStop (0.00s) CoverageTotal coverage: 🟩🟩🟩🟥 79.0% Coverage Details
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A hint that -user-cert
/-user-key
is only supported when using openconnect >= 9 might be a good idea.
f418ddc
to
684779d
Compare
Add the command line arguments "-user-cert" and "-user-key" to oc-client and the options "UserCertificate" and "UserKey" to the client config to support multi-certificate authentication. Signed-off-by: hwipl <[email protected]>
684779d
to
db39ba4
Compare
Yes, I added a note to both command line arguments that OpenConnect v9.00 or higher is required. |
Add the command line arguments "-user-cert" and "-user-key" to oc-client and the options "UserCertificate" and "UserKey" to the client config to support multi-certificate authentication.