Custom AWS credential provider must be used before all other credential fetching mechanisms

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Authentication
    • None
    • Hide

      DRIVERS-3207:
      Summary of necessary driver changes

      • Drivers must now ensure that when they allow a custom AWS credential provider to be supplied to the MongoClient, that it is only superseded in precedence by username/password/session key credentials provided in the URI or directly to the MongoClient.
      • Drivers must implement the new prose tests in the linked commit below.

      Commits for syncing spec/prose tests
      (and/or refer to an existing language POC if needed)

      Context for other referenced/linked tickets

      •  
      Show
      DRIVERS-3207 : Summary of necessary driver changes Drivers must now ensure that when they allow a custom AWS credential provider to be supplied to the MongoClient, that it is only superseded in precedence by username/password/session key credentials provided in the URI or directly to the MongoClient. Drivers must implement the new prose tests in the linked commit below. Commits for syncing spec/prose tests (and/or refer to an existing language POC if needed) Implement new AWS auth prose tests and client side encryption prose tests from https://github.com/mongodb/specifications/commit/4a46628a9efbc68d58134341b69be7ac1f5fada5 Context for other referenced/linked tickets  
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This ticket was split from DRIVERS-3207, please see that ticket for a detailed description.

            Assignee:
            Unassigned
            Reporter:
            TPM Jira Automations Bot
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: