Skip to content
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

Two Factor Web Dav: No certificate available to select to authenticate with #8299

cyberduck opened this issue Oct 31, 2014 · 1 comment


Copy link

@cyberduck cyberduck commented Oct 31, 2014

9108599 created the issue

This is a duplicate of #8234, which has been closed as worksforme.

I have the exact same symptom and found the root cause. I will detail the root cause below and steps I did to resolve it. I have downloaded the source and modified it to get it to work.

Symptom: When trying to connect to a webdav server with two-factor authentication enabled windows is unable to find any certificates in the personal store to use to authenticate with, even when the root ca cert is installed in the trusted root CA path in windows cert manager.

Root Cause: The windows certificate manager uses EMAILADDRESS (tokenised as E=) in the distinguished name when querying for certificates. RFC1779 states that EMAILADDRESS should be emitted as a OID. The implementation of Keychain.cs uses X500Principal.RFC1779 to get the distinguished name of the certificate issuer. When the issuer root ca cert has EMAILADDRESS specified the resulting DN string uses the OID representation of EMAILADDRESS and so it never finds a corresponding signed cert that matches that issue DN.

Work around: Don't use EMAILADDRESS in the root ca cert or issued signed certificates (this is probably why you closed it as worksforme)

I have attached a modified Keychain.cs that I used to get it to work. I know my solution probably isn't the most robust approach, but for now it works for me. I simply took the issuer.toString and escaped the EMAILADDRESS= as E=, rather than using an X500Principal.getName call.


Copy link
Collaborator Author

@cyberduck cyberduck commented Oct 31, 2014

@dkocher commented

In c41c969.


@cyberduck cyberduck closed this Oct 31, 2014
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants