[SERVER-23796] Incorrect warning when using mongos with keyfile: Access control is not enabled for the database Created: 19/Apr/16  Updated: 23/Nov/16  Resolved: 20/Apr/16

Status: Closed
Project: Core Server
Component/s: Security, Sharding
Affects Version/s: 3.2.5
Fix Version/s: 3.2.6, 3.3.5

Type: Bug Priority: Minor - P4
Reporter: Mingming Zhang Assignee: Shane Harvey
Resolution: Done Votes: 0
Labels: code-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-23799 Authorization check Closed
Related
Backwards Compatibility: Fully Compatible
Backport Completed:
Participants:

 Description   

Updated to version 3.2.5 today:
Warning in mongos at start up or at connection on it, whereas authentification is enabled on mongod and mongos (via a keyfile) :

2016-04-19T09:39:51.226+0200 I CONTROL  [main] ***** SERVER RESTARTED *****
2016-04-19T09:39:51.232+0200 I CONTROL  [main]
2016-04-19T09:39:51.232+0200 I CONTROL  [main] ** WARNING: Access control is not enabled for the database.
2016-04-19T09:39:51.232+0200 I CONTROL  [main] **          Read and write access to data and configuration is unrestricted.
2016-04-19T09:39:51.232+0200 I CONTROL  [main]
2016-04-19T09:39:51.268+0200 I CONTROL  [mongosMain] db version v3.2.5
2016-04-19T09:39:51.268+0200 I CONTROL  [mongosMain] git version: 34e65e5383f7ea1726332cb175b73077ec4a1b02
2016-04-19T09:39:51.268+0200 I CONTROL  [mongosMain] OpenSSL version: OpenSSL 1.0.1k 8 Jan 2015
2016-04-19T09:39:51.268+0200 I CONTROL  [mongosMain] allocator: tcmalloc
2016-04-19T09:39:51.268+0200 I CONTROL  [mongosMain] modules: none
2016-04-19T09:39:51.268+0200 I CONTROL  [mongosMain] build environment:
2016-04-19T09:39:51.268+0200 I CONTROL  [mongosMain]     distmod: debian71
2016-04-19T09:39:51.268+0200 I CONTROL  [mongosMain]     distarch: x86_64
2016-04-19T09:39:51.268+0200 I CONTROL  [mongosMain]     target_arch: x86_64

MongoDB shell version: 3.2.5
Enter password:
connecting to: xxxxx
Server has startup warnings:

2016-04-19T11:34:02.080+0200 I CONTROL  [main]
2016-04-19T11:34:02.080+0200 I CONTROL  [main] ** WARNING: Access control is not enabled for the database.
2016-04-19T11:34:02.080+0200 I CONTROL  [main] **          Read and write access to data and configuration is unrestricted.
2016-04-19T11:34:02.080+0200 I CONTROL  [main]

No configuration changed.

For comparaison purpose, version 3.2.4 :

2016-04-11T12:55:06.566+0200 I CONTROL  [main] ***** SERVER RESTARTED *****
2016-04-11T12:55:06.603+0200 I CONTROL  [mongosMain] db version v3.2.4
2016-04-11T12:55:06.603+0200 I CONTROL  [mongosMain] git version: e2ee9ffcf9f5a94fad76802e28cc978718bb7a30
2016-04-11T12:55:06.603+0200 I CONTROL  [mongosMain] OpenSSL version: OpenSSL 1.0.1k 8 Jan 2015
2016-04-11T12:55:06.603+0200 I CONTROL  [mongosMain] allocator: tcmalloc
2016-04-11T12:55:06.603+0200 I CONTROL  [mongosMain] modules: none
2016-04-11T12:55:06.603+0200 I CONTROL  [mongosMain] build environment:
2016-04-11T12:55:06.603+0200 I CONTROL  [mongosMain]     distmod: debian71
2016-04-11T12:55:06.603+0200 I CONTROL  [mongosMain]     distarch: x86_64
2016-04-11T12:55:06.603+0200 I CONTROL  [mongosMain]     target_arch: x86_64



 Comments   
Comment by Githook User [ 20/Apr/16 ]

Author:

{u'username': u'ShaneHarvey', u'name': u'Shane Harvey', u'email': u'shane.harvey@mongodb.com'}

Message: SERVER-23796 Fix incorrect access control startup warning

(cherry picked from commit 3f86bc56c7e3e9c69ab0725e2b140a1d1f138062)
Branch: v3.2
https://github.com/mongodb/mongo/commit/a88714f7c6010162279fe3897a07156fa124e06b

Comment by Githook User [ 19/Apr/16 ]

Author:

{u'username': u'ShaneHarvey', u'name': u'Shane Harvey', u'email': u'shane.harvey@mongodb.com'}

Message: SERVER-23796 Fix incorrect access control startup warning
Branch: master
https://github.com/mongodb/mongo/commit/3f86bc56c7e3e9c69ab0725e2b140a1d1f138062

Comment by Andreas Nilsson [ 19/Apr/16 ]

Thanks for your report mzhang. We will address this asap.

Regards,
Andreas

Generated at Thu Feb 08 04:04:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.