[SERVER-10640] Auth passthrough system should add admin user to non replica set shards when setting up a sharding test Created: 28/Aug/13 Updated: 11/Jul/16 Resolved: 13/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security, Sharding, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 2.6.0-rc2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Currently when a ShardingTest is setup under auth passthrough, if the shard is a replica set an admin user for use by the auth passthrough system gets added to the shard primary. If the shard is a standalone or master/slave, however, the admin user doesn't get added. This means that if the test tries to make a direct connection to the shard and do anything, it will get "unauthorized" errors as the auth system was unable to authenticate the connection since no admin user exists. |
| Comments |
| Comment by Githook User [ 14/Mar/14 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Githook User [ 13/Mar/14 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: |
| Comment by Spencer Brody (Inactive) [ 13/Mar/14 ] |
|
this issue was eliminated as part of the work done to fix All that remains to close out this ticket is to re-enable sharding/trace_missing_docs_test.js |
| Comment by Spencer Brody (Inactive) [ 29/Aug/13 ] |
|
Remember to re-enable sharding/trace_missing_docs_test.js in auth passthrough once this is fixed. |
| Comment by auto [ 29/Aug/13 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@10gen.com'}Message: |