[SERVER-11799] Issues with AddUser after upgrade to 2.5 Created: 20/Nov/13  Updated: 10/Dec/14  Resolved: 22/Nov/13

Status: Closed
Project: Core Server
Component/s: Security
Affects Version/s: 2.5.4
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Manojit Paul Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

dev / Linux opensuse 12.2 x86-64


Operating System: ALL
Participants:

 Description   

> db.addUser(

{ user: "developer", ... pwd: "xxxx123", ... roles: [ "readWrite", "dbAdmin" ] ... }

)
WARNING: The 'addUser' shell helper is DEPRECATED. Please use 'createUser' instead
2013-11-20T15:25:06.708-0600 Error: couldn't add user: User and role management commands require auth data to have schema version 3 but found 1 at src/mongo/shell/db.js:1016
>

What steps was missed when I just started the new engine ver 2.5.4 from
2.4.5 with the old db file ,.
Why is it complaining about schema ver 3 and 1 etc.

Also I could not find the syntax in doc for createUser too to try fixing this.



 Comments   
Comment by Spencer Brody (Inactive) [ 22/Nov/13 ]

I'm going to go ahead and close this out, if you continue to encounter problems after upgrading the user data to the new schema, feel free to re-open.

Comment by Spencer Brody (Inactive) [ 20/Nov/13 ]

Hi Manojit,
After upgrading to 2.5.4, user data is read-only until you upgrade the access control information to the new format. See http://docs.mongodb.org/master/release-notes/2.6/#authentication-and-authorization-incompatibility and http://docs.mongodb.org/master/release-notes/2.6-upgrade/#upgrade-from-mongodb-2-4-user-authorization-model-to-mongodb-2-5-x-model/ for more information on upgraded to the new scheme for access control data.

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