Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!

Not possible to reload from MongoDB with a non admin user with the Qlik MongoDB connector Qlik Sense version November 2020

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Andreas_Giesbrecht

Not possible to reload from MongoDB with a non admin user with the Qlik MongoDB connector Qlik Sense version November 2020

Last Update:

Jan 26, 2021 2:30:29 AM

Updated By:

Sonja_Bauernfeind

Created date:

Jan 19, 2021 5:53:38 AM

Some customers reported the following error with the Qlik MongoDB connector (within the ODBC connector package) after upgrade to Qlik Sense version November 2020: 

Error: Connector reply error: Unable to connect to database:
20201216T110846.906+0100 Error message:
20201216T110846.906+0100 Please check the values for Username‚ Password‚ Host and other properties.

The issue could be seen and also could be reproduced when you use a non admin MongoDB user in order to reload the data from the MongoDB database (version 3.6).

For more information please check the screenshot:

mongo DB test QS Nov 2020 - non admin user v01.PNG

 When you replaced the user for the MongoDB connection with an admin user the reload was working again:

mongo DB test QS Nov 2020 - admin user v01.PNG

Environment

 

Cause 

As a result of the investigation:

1) On the reproduction environment we had two users with the same name (here for example "tester") specified in two DB: "admin" and "test_db1" (they had different passwords).

2) Driver from June 2020 release(v. 2.3.7) tried check credentials first for a "tester" from admin DB (as a default) and next from "test_db1" and as credentials fit ok connect by this  user.

3) After fix: Driver from November 2020 release(v. 2.3.12) tried check credentials for "tester" from admin DB (as a default) then connection failed due to credentials does not fit for "tester" from "admin" db.

 

Resolution

 To specify a user from which particular DB we are trying to use we need to use the additional parameter "AuthSource", like on screenshot:

image (2).png

 

 

 

Labels (2)
Version history
Last update:
‎2021-01-26 02:30 AM
Updated by: