Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add User dialog creates invalid users that won't actually work to auth with MongoDB #1041

juliashibalko opened this issue Feb 25, 2016 · 27 comments


Copy link

@juliashibalko juliashibalko commented Feb 25, 2016

Robomongo versions checked: 0.8.5 at first, then latest 0.9.0-RC4


Steps:(Windows version)

  • MongoDB version 2.6.11
  • Connect to a DB
  • Expand to the Users folder
  • Right-click and choose Add User
  • Enter Username and Password; select a few roles
  • Click OK
  • Note that the User document appears as a child under the Users folder in the left pane
  • Right-clicking on the Users folder and choosing View Users will display the created User. Note that the command executed is db.system.users.find()
  • Test auth by entering db.auth('<username>', '<password>') into the console
  • Observe that the response is Error: auth failed 0

You can create a user that does work with db.auth() by using db.createUser(). You can list these users with db.getUsers().

Copy link
Collaborator Author

@juliashibalko juliashibalko commented Feb 26, 2016

@AdamAndersonFalafelSoftware Thanks Adam for adding details! We'll address that in the upcoming releases.

Copy link
Collaborator Author

@juliashibalko juliashibalko commented Aug 16, 2016

Copy link

@christangga christangga commented Dec 23, 2016

is this solved in the new release?

Copy link

@simsekgokhan simsekgokhan commented Dec 26, 2016

Hi @christangga , unfortunately not, the current heavy weight work is delivering critical features like Replcia Sets and Export/Import asap. User management is planned to after those.
Please see here:

Copy link

@Aninstance Aninstance commented Jun 13, 2017

This issue still persists, Robomongo 1.0.0, MongoDB 2.6.12.

Copy link

@rocketkittens rocketkittens commented Aug 3, 2017

Issue persists with Robo 3T 1.1.1 (mac) and MongoDB 3.4.6 ('db version' from mongod -v)

Was not able to use Robo 3T 'Explorer' to create users via 'Add User...' option on 'admin' db 'Users' collection right-click menu.

Had to use db.CreateUser() and then manually craft the document/bson.

screen shot 2017-08-03 at 7 27 33 pm

Copy link

@Kroderia Kroderia commented Sep 14, 2017

Same issue as @Alandroid with Robo 3T 1.1.1 (Windows 10) and Mongodb 3.2.13

Copy link

@dickreuter dickreuter commented Nov 26, 2017

Still not solved

Copy link

@hiasel hiasel commented Nov 27, 2017

Unfortunately the issue is still not solved.
Robo3T: Version 1.1.1 for Mac
Mongo: 3.4.10

As @Alandroid pointed out, a current workaround is to create users inside the command-window of Robot3T. Adding a user called "myuser" to the db "mydb" looks like this:

use mydb
db.createUser( { user: "myuser",
                 pwd: "mypw",
                 roles: [ { role: "readWrite", db: "mydb" }] },
               { w: "majority" , wtimeout: 5000 } 


Copy link

@rtf6x rtf6x commented Apr 5, 2018

Still not solved

Copy link

@dejayc dejayc commented Apr 25, 2018

If this joke of a feature is still not implemented two years later, maybe the developers should just remove the "Add User" option from the menu?

Copy link

@nanomo nanomo commented Aug 2, 2018

Still not solved, lost big time with this bug, please add at least a modal warning with a message!

Copy link

@vetinary vetinary commented Aug 6, 2018

OH! MY! GOD! It took me half a day to find this topic and find out, that problem was not in my software, but in Robo 3T app. 🤦‍♂️

Copy link

@Tarpsvo Tarpsvo commented Aug 20, 2018

Well, I joined the lost two hours past midnight club here. This should be high priority.

Copy link

@NobleZirwaHara NobleZirwaHara commented Sep 4, 2018

Really though??? Why is it even there in the first place. Goodness

Copy link

@dejayc dejayc commented Sep 4, 2018

It's there to confuse new users for years on end.

Copy link

@ardennext99 ardennext99 commented Oct 15, 2018

Still present in my configuration:

Robo 3T 1.2.1 + MongoDB 2.7.0

If I create an user in Robo 3T by "Add user" function, I cannot find it by "db.getUsers()" command line.
If I create an user by command line, when i refresh the Robo 3T users compaer "mongodb wrong type for field (_id) string = 7"

When we can hope a fix?
Robo 3T should be the "Sql Server Management Studio" for MongoDB, but with this bug.....

Copy link

@chrisp3r chrisp3r commented Oct 22, 2018

Also having this issue. When I create a user from the shell, no problem, but using the GUI the user created is not able to authenticate. v1.2.1

Copy link

@rocketkittens rocketkittens commented Oct 22, 2018

Still not solved. This software is outdated.

Copy link

@macxu macxu commented Nov 14, 2018

still not solved.... I spent more than an hour on it and it turned out to be a known issue on the software...

Copy link

@PathToLife PathToLife commented Jan 2, 2019

Wasted 2 hours of my time. Rip. Is this fixed in the overpriced Studio3T?

Copy link

@PathToLife PathToLife commented Jan 2, 2019

Hey fix found

simsekgokhan added a commit that referenced this issue Feb 2, 2019
…abling user source and password mutual exclusivity.
simsekgokhan added a commit that referenced this issue Feb 5, 2019
…I database explorer previously not visible users are now visible. And removing unused MongoUser code.
Copy link

@simsekgokhan simsekgokhan commented Feb 17, 2019

Hi All, we are very sorry for the long delay.
We have some fixes and new features related to user management. Currently, the limitation is Robo supports fixed usersource for user creation. Please try our beta:

Robo 3T 1.3 Beta

Copy link

@september28 september28 commented Mar 20, 2019

Hi Guys, I have suffered this same issue. Is there a way I can remove the erroneous user that Robo3T has created? I don't seem to have permissions to delete the user now, and I am left with a "System" folder in the (relevant) database containing a "system.users" collection, and a "Users" folder under the database with my erroneous user. If I try to right click the user and click "Drop User" I get the message "Failed to drop user 'username-here'. Error: Not authorized to remove from database-name.system.users".
in the CLI:
use database-name
produces an empty array so mongodb itself can't seem to delete it...

Any help appreciated.

Copy link

@brucecollins brucecollins commented May 13, 2020

I'd say this is a bit of an issue as I spent an entire day troubleshooting this capability. Is there any chance robo3T UI can disable the function to avoid sending others on a wild goose chase? Lastly, if robo3t is not a viable Ui - which one should I install and use? Thanks!

Copy link

@simsekgokhan simsekgokhan commented May 27, 2020

Hi @september28 , @brucecollins . Very sorry to hear that you wasted your time.
To fix (or disable that functionality) can you tell us how to reproduce your problems?

  • Steps to reproduce
  • Robo 3T version
  • MongoDB version and db details (Atlas, local, single, replica set etc..)
  • OS version (Win 7, Ubuntu 18.04 etc..)

Please also note that we have some users related fixes on Robo 3T 1.3

I just created a user on my local server. Connection works, I can drop the user and can see the created user:

> use admin
switched to db admin
> db.getUsers()
               "_id" : "",
               "userId" : UUID("9c98b305-94a3-4c94-b1a1-3e04d21f8e59"),
               "user" : "bb",
               "db" : "admin",
               "roles" : [
                               "role" : "readWriteAnyDatabase",
                               "db" : "admin"
               "mechanisms" : [
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Robo 3T 1.3
Awaiting triage
Linked pull requests

Successfully merging a pull request may close this issue.

None yet