![\"InvalidCredentials\"](\"http:\/\/www.theSQLReport.com\/wp-content\/uploads\/2013\/10\/InvalidCredentials.jpg\")
<\/a><\/p>\nIn this case, I had two issues with to resolves before I could connect and administer the ‘pcat’ database:<\/p>\n
1. Configure the MongoDB software to authenticate for remote connections.<\/p>\n
2. Create a user that I can authenticate in the ‘pcat’ database.<\/p>\n
——————————————————————————————————<\/p>\n
The first step is to alter the configuration file that the process ‘mongod’ is using.\u00a0 On the server, by running ‘ps -ef | grep mongod’, I was able to see that the process was using the configuration file ‘mongodb.conf’ that resided in the ‘\/etc’ directory.\u00a0 The configuration file may reside in a different location based on your operating system & configuration at setup.<\/p>\n
Using an editor on that file (like vi), I was able to see that the authentication parameter for remote users was remarked out.\u00a0 I removed the pound sign in front of the “auth = true”, and saved the file.\u00a0 Then I restarted the Mongod process by typing “sudo service mongodb restart”.\u00a0 Now remote users are able to authenticate to the database.<\/p>\n Second, we need a user that is permitted to access the database remotely.\u00a0 In the Mongo shell I had to switch to the ‘pcat’ database, by typing “use pcat”.\u00a0 Then I added a user with the command db.addUser, like db.addUser(” <username> ” , ” <password> “).\u00a0 In my example, I used “buddy” for both the name & password.\u00a0 I then verified the user with the “show users” command.<\/p>\n After creating the user, I was able to go back to my MongoVUE application, and enter the connection information in the “MongoVUE Connection”, with an example pictured below.<\/p>\n Then I was able to successfully connect to the MongoDB database, and view the Collections.<\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\n