[Epic] Custom SSL support in source-mongodb-v2 (to SSH & SSL support AWS documentDB)

[rodireich]

Connector Name

source-mongodb-v2

Connector Version

1.0.11

What step the error happened?

Configuring a new connector

Relevant information

No response

Relevant log output

MongoDB instances may be using a certificate that is not publicly trusted.
In the connection string it is possible to specify a CA to trust:

tlsCAFile=…/global-bundle.pem

In addition a customer can also authenticate using a client certificate.

Implement all possible SSL features the driver supports, similarly to other connectors.
[ref]

### Contribute

- [ ] Yes, I want to contribute

[rodireich]

#10388 has a hard coded implementation that bakes a CA pem file into the connector.

[rodireich]

Also AWS DocumentDB instances come out of the box with a CA that is not publicly trusted and hence has to be specified to the connector to be able to connect.

[klawecki]

@rodireich are there any chances to address this issue in upcoming weeks?

[rodireich]

@klawecki we're looking into this issue and will update as we have more clarity.
Can I ask in the meantime what your use case here is?
Are you using aws DocumentDB?

[thepr0blem]

@rodireich yes

[evantahler]

Linking related issues:

• MongoDB: Support SSL connection and allow paste SSL PEM file content #7379
• Mongodb TLS Connection Problem #35657
• Source MongoDB: cann't connect to TLS enabled Amazon DocumentDB #10388

[evantahler]

Are any of the members of the Airbyte community on this issue interested in working on this issue?