[SERVER-15337] All authentication fails when auth schema version 4 used with SCRAM as only mechanism Created: 19/Sep/14  Updated: 02/Aug/18  Resolved: 24/Sep/14

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

Type: Task Priority: Major - P3
Reporter: John Morales Assignee: Gregory McKeon (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-15179 Upgrade/downgrade steps MONGODB-CR ->... Closed
Participants:

 Description   

Encountered against Amazon SSL 64-bit 2.7.7-pre build from this morning. (at commit 986d4a410e).

When authSchemaVersion=4 is used together with --setParameter authenticationMechanisms=SCRAM-SHA-1, authentication on the shell always fails, even when explicitly specifying the mechanism.

For example:

> use admin
> db.auth({user:"admin", pwd:"foo", mechanism:"SCRAM-SHA-1"})
Error: 18 Authentication failed.
0

The server log contains the following message on each failed attempt when specifying the mechanism:

2014-09-19T20:36:57.602+0000 I ACCESS   [conn4] SCRAM-SHA-1 authentication failed for admin on admin ; BadValue Illegal value for authorization data schema version, 4



 Comments   
Comment by Githook User [ 24/Sep/14 ]

Author:

{u'username': u'agralius', u'name': u'Andreas Nilsson', u'email': u'andreas.nilsson@10gen.com'}

Message: SERVER-15337 Improved handling of schemaVersion28SCRAM
Branch: master
https://github.com/mongodb/mongo/commit/a553643b019b0f2901a8e6a109482acb5cb0a18f

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