Files
mongo/jstests/sharding/auth_copydb.js
Kaloian Manassiev b6abb408c1 SERVER-24603 Re-enable auth tests in 'sharding_last_stable_mongos'
This change makes auth tests with 3.2 mongos, which need to control the
balancer state to go through a special control mongos instance running
version 3.4.

This reverts commit bfde0ecb1c.
2016-06-20 22:15:57 -04:00

41 lines
1.3 KiB
JavaScript

// Tests the copydb command on mongos with auth
(function() {
'use strict';
var st = new ShardingTest({shards: 1, mongos: 1, other: {keyFile: 'jstests/libs/key1'}});
var mongos = st.s0;
var destAdminDB = mongos.getDB('admin');
var destTestDB = mongos.getDB('test');
var sourceMongodConn = MongoRunner.runMongod({});
var sourceTestDB = sourceMongodConn.getDB('test');
sourceTestDB.foo.insert({a: 1});
destAdminDB.createUser({
user: 'admin',
pwd: 'password',
roles: jsTest.adminUserRoles
}); // Turns on access control enforcement
jsTestLog("Running copydb that should fail");
var res = destAdminDB.runCommand(
{copydb: 1, fromhost: sourceMongodConn.host, fromdb: 'test', todb: 'test'});
printjson(res);
assert.commandFailed(res);
destAdminDB.auth('admin', 'password');
assert.eq(0, destTestDB.foo.count()); // Be extra sure the copydb didn't secretly succeed.
jsTestLog("Running copydb that should succeed");
res = destAdminDB.runCommand(
{copydb: 1, fromhost: sourceMongodConn.host, fromdb: 'test', todb: 'test'});
printjson(res);
assert.commandWorked(res);
assert.eq(1, destTestDB.foo.count());
assert.eq(1, destTestDB.foo.findOne().a);
st.stop();
})();