CData for MongoDB JDBC error Authentication failed

Live Connectivity CData Drivers
, ,
1

I’ve downloaded JDBC driver for MongoDB but when using it with the correct username password, it throws the error:

Exception in thread “main” java.sql.SQLException: Failed to authenticate database ‘testdb’, Error code: [18] - “Authentication failed.”..

        Class.forName("cdata.jdbc.mongodb.MongoDBDriver");        Properties prop = new Properties();        prop.setProperty("Server","127.0.0.1");        prop.setProperty("Port","27017");        prop.setProperty("Database","testdb");        prop.setProperty("User","useradmin");        prop.setProperty("Password","welcome!");        Connection conn = DriverManager.getConnection("jdbc:mongodb:", prop);        Statement stat = conn.createStatement();        boolean ret = stat.execute("SELECT name FROM users");

It throws error on the last line. These username password are correct and can be used in mongosh inside mongo server container

2

Hi @quangdutran809

Thanks for reaching out on CData Community!

By looking at your issue, I can think of two areas to investigate:

1.) Check if the User - ‘useradmin’ is created under Database - ‘testdb’ and has access to the database. Mostly, the users created under ‘admin’ database face such issues.

2.) Check again if the credentials are correct, you are using right cases, and there are no whitespaces.

3

Hi @quangdutran809 ,

One thing that I wanted to add is the utilization of AuthDatabase connection property. I was able to replicate the same issue as you, but after setting this property, I was able to get data from mongoDB.

6931f0c7-4336-4717-bec1-f9b303f23b7d.png
6931f0c7-4336-4717-bec1-f9b303f23b7d.png1032×882 95.5 KB

I would also recommend you specify the AuthScheme as well.

Give this method a try and let me know how it goes.

4

Thanks @Ankit_Singh  I think the user that I am using is the root user, which should have permissions on all db, this is how I set up that user in Docker:

FROM mongo:7.0.2ENV MONGO_INITDB_ROOT_USERNAME adminuserENV MONGO_INITDB_ROOT_PASSWORD welcome!ENV MONGO_INITDB_DATABASE testdb

Also, using MongoDB Compass with that user, I can browse dbtest normally.

Thanks @Luçjano Capo, seem legit but I’ve added both `AuthScheme` and `AuthDatabase` but it still gives the same error 😪

119c9a6a-989f-4c42-9ed5-14dc1cf9efe8.png
119c9a6a-989f-4c42-9ed5-14dc1cf9efe8.png1222×572 76.4 KB

5

Ah I’ve just realized that I’ve use the wrong username but adding `AuthDatabase` really solves the issue. Thanks guys, maybe this should be added to the document?

6

Hi @quangdutran809
I think it is part of the documentation here: CData JDBC Driver for MongoDB - Establishing a Connection. Since there are different Auth Schemes, it can be a bit confusing.

7

Hi Team,
I am trying to connect my MongoDB Cluster using JDBC driver.
But I am getting below exception.
 (java.sql.SQLException) java.sql.SQLException: Unable to connect to cluster0.yw4hs.mongodb.net:27017: System error: UnknownHostException - No such host is known (cluster0.yw4hs.mongodb.net)

Can you please help me .

8

Hi ​ @kumar88

The error message you are getting "Unable to connect to cluster0.yw4hs.mongodb.net:27017: System error: UnknownHostException - No such host is known" would indicate that your MongoDB instance is unreachable which would be due to an issue caused by the Server connection property. Can you confirm you are setting the correct value for the Server property? Can you confirm your MongoDB instance is running and accessible? You can verify this by executing a ping request against your server within the command prompt.

There are also a couple of other things to take in consideration. Perhaps you are you trying to connect to a Mongo instance using DNS seed list?

If so the Server connection should be set as follows:

Server=mongodb+srv://cluster0.****.mongodb.net;

Please note that the the use of SRV records eliminates the requirement for every client to pass in a complete set of state information for the cluster. Instead, a single SRV record resolves all the nodes associated with the cluster (and their port numbers) through the DNS Server. You can read more here:

Alternatively, it could be that you are connecting to a ReplicaSet and for this reason you might need to fill in the proper connection properties to allow the MongoDB driver to access secondary Mongo nodes as well. You can read more about this here: CData JDBC Driver for MongoDB - Establishing a Connection

If you have any other questions feel free to reach out to the CData support team at support@cdata.com.