[SERVER-32971] Wrap existing SASL mechanisms into SASL mechanism Registry Created: 29/Jan/18  Updated: 27/Oct/23  Resolved: 10/Mar/18

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

Type: Improvement Priority: Major - P3
Reporter: Spencer Jackson Assignee: Spencer Jackson
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Platforms 2018-02-12, Platforms 2018-02-26, Platforms 2018-03-12
Participants:

 Description   

The existing SASL mechanism classes must be adapted for use in the SASL mechanism registry.

The following mechanisms must be adapted:

  • SCRAM-SHA-1 (This Mechanism must override the client instance factory to inject a reference to a SCRAM client credential cache).
  • GSSAPI (Both the SSPI and GSSAPI implementations)
  • PLAIN (Internal, LDAP Native, and Cyrus SASL/Saslauthd)


 Comments   
Comment by Spencer Jackson [ 10/Mar/18 ]

This work was accomplished in SERVER-32966. To fully scope out how the API for the mechanism registry would work, existing mechanisms had to be ported over to use the registry. This obviated the need for a temporary shim.

Generated at Thu Feb 08 04:31:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.