Validate X.509 Auth when Intermediate Cert is not placed in Atlas

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Cannot Reproduce
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Authentication
    • None
    • None
    • Dotnet Drivers
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      The MongoDB .NET/C# driver behaves differently compared to Compass when using X.509 Authentication. The following scenario summarizes the behavior: 

      • Root and Intermediate Cert placed in Atlas
        • MongoDB Compass: Providing Client-Key + Client-Cert
        • C# Drivers: Providing Client-Key + Client-Cert
      • Root Cert placed in Atlas
        • MongoDB Compass: Providing Client-Key + Client-Cert + Intermediate Cert
        • C# Drivers: Providing Client-Key + Client-Cert + Intermediate Cert

      A/C:

      • We need to validate if the 4th scenario is expected behavior and if so document why. If it isn't then the issue should be fixed.  

            Assignee:
            Damien Guard
            Reporter:
            Rishit Bhatia
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: