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.

Sign up for GitHub

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

Jump to bottom

TOOLS-2598 Fix client certificate chain bug #429

Merged
merged 3 commits into from
Apr 7, 2023
Merged

TOOLS-2598 Fix client certificate chain bug #429

merged 3 commits into from
Apr 7, 2023

Commits on Apr 4, 2023

  1. Fix client certificate chain bug 

    If the user provides a client certificate chain (i.e., a client cert + an
intermediate cert), currently mongodump will ignore all certs except the last
one (i.e., dropping the client cert) and then compare the intermediate cert to
the private key, resulting in a fatal error about the key and the cert not
matching. Additionally, since we drop all but the last cert, we don't present
the server with the correct client cert.

Here we append all certs in the cert/key file together + use the first cert for
the subject name, which is standard practice. This fixes X.509 auth for
mongodump.
    @mukerjee @edobranov
    mukerjee authored and edobranov committed Apr 4, 2023
    Configuration menu
    Copy the full SHA
    7819a97 View commit details
    Browse the repository at this point in the history

  2. Use driver fix and add test

    @edobranov
    edobranov committed Apr 4, 2023
    Configuration menu
    Copy the full SHA
    9b1e4d0 View commit details
    Browse the repository at this point in the history

  3. Remove test

    @edobranov
    edobranov committed Apr 4, 2023
    Configuration menu
    Copy the full SHA
    449df66 View commit details
    Browse the repository at this point in the history