[DOCS-11603] Docs for SERVER-34446: Remove SASLPrep normalization of principal names used in SCRAM-SHA-256 Created: 13/Apr/18  Updated: 12/May/18  Resolved: 12/May/18

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 3.7.4

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-34446 Remove SASLPrep normalization of prin... Closed
Duplicate
Participants:
Days since reply: 5 years, 43 weeks, 5 days ago
Epic Link: DOCS: 4.0 Server

 Description   

Documentation Request Summary:

No documentation summary in engineering ticket

Engineering Ticket Description:

Principal names should be treated as in SCRAM-SHA-1. The server should:

1) Not perform normalization of usernames during SCRAM-SHA-256
authentication. Usernames provided by clients would be used as-is. This
is the behavior of SCRAM-SHA-1 today.
2) Continue to normalize passwords when used with SCRAM-SHA-256. This
is more important that the normalization of user names. The byte
representation of user names can be recovered from the database itself.
The byte representation of the password cannot, after it's been
processed into a credential.
3) Allow createUser to be performed on a SCRAM-SHA-256 user with an
unnormalized name.


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