[SERVER-9009] mongodump fails when run by a read-only user Created: 18/Mar/13  Updated: 10/Dec/14  Resolved: 18/Mar/13

Status: Closed
Project: Core Server
Component/s: Admin
Affects Version/s: 2.2.2
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Matthew Parsons Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: mongodump
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CentOS 6.3 x86_64


Issue Links:
Duplicate
duplicates TOOLS-134 Mongodump and mongoexport should skip... Closed
Related
related to SERVER-4692 Read-only users should be denied acce... Closed
Operating System: Linux
Steps To Reproduce:

Connect to Mongo:
use admin
db.addUser("backup","xxxxx",true)
exit

  1. mongodump --host localhost:27018 -u backup -p xxxxx -o .
    connected to: localhost:27018
    Mon Mar 18 15:03:09 DATABASE: xxxxx to ./xxxxx
    Mon Mar 18 15:03:09 xxxxx.system.users to ./xxxxx/system.users.bson
    assertion: 11010 count fails: { assertion: "unauthorized db:xxxxxx ns:xxxxx.system.users lock type:1 client:127.0.0.1", assertionCode: 10057, errmsg: "db assertion failure", ok: 0.0 }

Setting the user read-only flag back to "false", and the backup will run successfully.

Participants:

 Description   

The mongodump command fails when it authenticates with a read-only user.

This appeared to work in an earlier version, and it would seem to be more secure to not have to use a backup user with write access.



 Comments   
Comment by Daniel Pasette (Inactive) [ 16/Jul/13 ]

this is a duplicate of SERVER-9012

Comment by Rick Cotter [ 12/Jul/13 ]

+1 (Can't seem to vote?)

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