-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: 3.0.1
-
Component/s: Security
-
None
-
Fully Compatible
-
ALL
-
-
Security 1 04/03/15
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Hi,
I am flagging this as a bug, as the mongod dev user google is full of people having problems with the 3.01 security configuration. People can't get into the web console or list databases or list users because of this bug. My hypothesis is when the disable auth option went away the replacement authorization is faulty. Here is my configuration file, using this I can connect but can't access the test db or admin db or create a user..or use webadmin
storage:
dbPath: "c:/data"
journal:
enabled: true
systemLog:
destination: file
path: "C:/mongologs/mongodb.log"
logAppend: true
net:
bindIp: 11.1.1.2
port: 27017
http.enabled: true
http.RESTInterfaceEnabled : true
security:
authorization: disabled
replication:
oplogSizeMB: 10240
replSetName: "rs1"