Open Sampad-Hegde opened 9 months ago
@Sampad-Hegde I'd strongly recommend to tag your new version as dev
instead of an official version.
I found this discussion about the error you got and maybe there are some code changes needed to be done to make the connector work properly with certificates. Maybe took a look in other connectors that support certifies how they're doing the implementation.
Unfortunately we encountered the same problem.
I wanted to disable verification in the form -Dcom.sun.jndi.ldap.object.disableEndpointIdentification=true
but did not find an vmoption to start the connector
Yes @sskhandek, I have tried setting it in JAVA_OPTS, as well as tried to set it in the env variable still it didn't get disabled.
@marcosmarxm I agree with you; but It's ok to give any tag to docker image while building/running in local, moreover I just want to test the connection and working piece of this connector, Then I would have done proper naming and setup. That stack overflow methods are tried already except changing the source code approach. You can see in my docker image build process.
Connector Name
source-mongodb-v2
Connector Version
1.2.4
What step the error happened?
Configuring a new connector
Relevant information
I am using
Self-Managed Replica Set
with 1 primary and 1 secondary both are deployed in separate VMs. and both VMs are accessible from my airbyte VM. This has a ssl enabled and it is self signed as well.I was able to connect from studio3T, mongosh as well as from Mongodb Compas by giving these ca.pem and client.pem files
Mongo1 : 20.42.3.5:7688 Mongo2 : 20.42.3.6:7688
mongo-uri:
mongodb://<usr_name>:<pwd>@20.42.3.5:7688,20.42.3.6:7688/<my_db>?replicaSet=asimongodevc1
added necessary data in username, password, Authentication Source etc.
I tried with and without these url params: ssl = true/false tls = true/false tlsAllowInvalidHostnames = true sslAllowInvalidHostnames = true
I Built the custom docker image, which is the extension of
airbyte/source-mongodb-v2
and adding my ca certificate to truststore/keystore.here is my custom image Dockerfile content:
building the image with this command:
docker build -t airbyte/source-mongodb-v2:1.2.4 . --no-cache --progress=plain
I have added SAN manually while adding to keystore but issue still persist: cmd used :
RUN $JAVA_HOME/bin/keytool -import -noprompt -trustcacerts -alias VymoProdDSCA -file /local/ca.pem -keystore $JAVA_HOME/lib/security/cacerts -storepass changeit -ext SAN=DNS:mongo1.vymo-priv.net,DNS:mongo2.vymo-priv.net,IP:20.42.3.5,IP:20.42.3.6
Error: With DNS
With IP:
Tried these as well none of them worked:
COMPLETE LOG IS ATTACHED
Relevant log output
ON ORIGINAL DOCKER IMAGE (airbyte/source-mongodb-v2:1.2.4): I am Getting This error:
Contribute