admin database for authentication

Rick Otten shared this question 10 months ago
Answered

How do I configured it to use the admin database for authentication, but then connect to the database with the data in it?

When I configure it to connect to the admin database, I get a "can't run a shell" error. When I configure it to connect to the data database, I get an authorization denied.

Comments (5)

photo
1

Hi Rick,


Firstly thanks for giving dbKoda a try!

Could you provide us with some additional information so we can try and diagnose this bug for you straight away, as you should be able to create a shell connection on your admin database.

Any of the following that you are happy to provide would be very helpful;

  • Operating System.
  • A screenshot of the error in question.
  • Can you access the Mongo Shell from your path?

Thanks!

Michael.

photo
1

I can access the mongo shell to my replica set using Studio-3T, and with the mongo command line. It just didn't work in dbKoda. I'm running on an Ubuntu 17.04 desktop (Gnome).

There isn't much to show as a screenshot. I get a red box that says "Error: authentication failed" when I try to connect directly to the database I'm interested in. When I change the Database field to "admin" I get a little more:

"Error: Create shell connection failed.

Please check your mongo binary path or define your own mongoCMD in ~/.dbKoda/config.yml"

"mongo" is in /usr/bin/mongo. I don't want to connect to the admin database anyhow, I want to connect to the data database, and just use the admin database for authentication.

photo
1

Hi Rick,


We're going to add a field to add a separate authentication database as soon as possible and will keep you updated, this should allow you to connect to your database while authenticating through admin.

However there also seems to be a separate bug at play here, one causing the product to fail detecting a Mongo Binary in your PATH environment variable. Apologies that you've encountered these troubles with the application.

We will continue to investigate and try and track the bug down. In the meantime, could you possibly please try these steps to help us isolate and resolve the issue;

Kind Regards,

Michael.

photo
1

Hi Rick,

Our pre-release build of the product has a separate field in our connection wizard to specify Authentication Database, if you don't specify any authentication database the product will default to try and authenticate through the Admin database. This build is a work in progress and may have some bugs or abnormal behaviours present, please don't hesitate to shout out if you encounter these so we can get on them right away.


Kind Regards,

Michael.

photo
1

The nightly (pre-release) builds can be found here: https://github.com/SouthbankSoftware/dbkoda/releases