-
-
Notifications
You must be signed in to change notification settings - Fork 431
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
CLI addUser requires db_uri if set for strider #1061
Comments
Hi, |
There is not a user after strider has been installed, so I want to add one. |
No users are installed with strider, it's supposed that the admin has to add it, as you did. Try it again after changing the debug mode. |
Below is the whole output:
strider:config { logging: |
Are there other databases in you mongo instance? The user create might have used a different database name.. |
Might be related to #1055 |
This DB is only for Strider. |
I experienced the similar case with a fresh install of Strider on AWS Linux 2. Problem was that by default MongoDB URL: is pointing to a database named 'strider-foss' rather than as in install instructions 'strider'. So you should be always remembering to set the DB_URI environment variable to point to the correct database when running |
Hum, that's a bug for sure. |
So not so much a bug, but unfortunate side effect of using envs. Maybe we should suggest using the file to configure instead of bare envs. |
Hi,
After installation I create a user with cli below:
[root@strider strider]# node bin/strider addUser
Connecting to MongoDB URL: mongodb://localhost/strider-foss
Enter email []: [email protected]
Enter password []: *******
Is admin? (y/n) [n]y
Email: [email protected]
Password: ****
isAdmin: y
OK? (y/n) [y]y
User created successfully! Enjoy.
And then I visit web site to login with this new user, but login failed as below:
Authentication failed, please supply a valid email/password.
Then I run command "db.users.find()" in strider db; however, there is no item.
So how to deal with this?
The text was updated successfully, but these errors were encountered: