You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 10, 2023. It is now read-only.
I think prima-facie it sounds like MongoDB thing as Tayra simply forwards the creds to MongoDB, but I'll ask the team to take a look into this. We will get back to you.
Also, it would be nice, if you could give us the steps to reproduce. Thanks!
Hi,
I think currently Tayra authenticates credentials only for "admin" database.
What we need to do is accept the "database" as well to authenticate against.
"By default, mongooplog assumes that the database specified to the --db argument holds the user’s credentials, unless you specify --authenticationDatabase."
Hi Rudolf,
I went through the issue, and --authenticationDatabase is introduced from 2.4 onwards. We are planning to introduce --authDb as a command line argument, which will take in the value for DB where credentials are stored.
For backward compatibility, ie for version below 2.4, we will keep --authDb parameter, and if user provides say '--authDB "someDB"', then too credentials will be looked for in 'admin' database.
For version >= 2.4, user will be authenticated using the authDb he specified.
Does this sounds good?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Tayra seems to always want to authenticate using 'admin' which makes it impossible to authenticate using db level users stored in .system.users .
It's also not possible to use the mongodb standard URI to connect to a db.
The text was updated successfully, but these errors were encountered: