[SERVER-7795] Support CRAM-MD5 and PLAIN SASL Mechanisms Created: 29/Nov/12  Updated: 02/Aug/18  Resolved: 03/Dec/12

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

Type: Task Priority: Major - P3
Reporter: Andy Schwerin Assignee: Andy Schwerin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Description   

This greatly facilitates testing, and may be desired by some customer.



 Comments   
Comment by auto [ 05/Dec/12 ]

Author:

{u'date': u'2012-12-05T22:27:37Z', u'email': u'spencer@10gen.com', u'name': u'Spencer T Brody'}

Message: Update comments to refer to $sasl instead of $external. SERVER-7795
Branch: master
https://github.com/mongodb/mongo/commit/7fbd3339d01880709000e533a26fdbd93c51fee9

Comment by auto [ 05/Dec/12 ]

Author:

{u'date': u'2012-12-05T00:16:12Z', u'name': u'Andy Schwerin', u'email': u'schwerin@10gen.com'}

Message: For SASL authentication in the client, send the saslStart/Continue commands to the right database.

For users whose credentials are stored externally, send the command to
"sasl", for all other users, send it to the database whose system.users
collection contains a document for the given user with a "pwd" field.

SERVER-7795
Branch: master
https://github.com/mongodb/mongo/commit/1e7a83f9f97e4ee92c65ec9d9758c479b56b89cf

Comment by Andy Schwerin [ 03/Dec/12 ]

The current implementation expects database users to be identified as "dbname$username", though we are in talks with driver team to find a more satisfactory solution.

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