[SERVER-8305] saslAuthenticate defaults to wrong database when using GSSAPI mechanism Created: 23/Jan/13 Updated: 19/Mar/13 Resolved: 08/Feb/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.3.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Craig Wilson | Assignee: | Andy Schwerin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
In a shell connected to subscriber edition 2.3.2 the following succeeds authentication but grants no privileges. The code is targeting the wrong userSource as a default. It should target $external, but currently targets $sasl.
The following works, but shouldn't be required.
|
| Comments |
| Comment by auto [ 12/Feb/13 ] |
|
Author: {u'date': u'2013-02-08T17:04:35Z', u'name': u'Andy Schwerin', u'email': u'schwerin@10gen.com'}Message: |
| Comment by Andy Schwerin [ 08/Feb/13 ] |
|
After db.auth continues to support the old (user, password) calling behavior, as well. |
| Comment by Craig Wilson [ 23/Jan/13 ] |
|
The release notes for 2.4 don't indicate that userSource is necessary. |