[DOCS-14151] Investigate changes in SERVER-52645: Allow userToDNMapper to accept (and use by default) an empty set of transforms Created: 22/Jan/21  Updated: 13/Nov/23  Due: 07/May/21  Resolved: 21/May/21

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.9.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Andrew Feierabend (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-52645 Allow userToDNMapper to accept (and u... Closed
Participants:
Days since reply: 2 years, 37 weeks, 5 days ago
Epic Link: DOCSP-9747
Story Points: 2

 Description   

Description

Downstream Change Summary

This change creates following new behavior as far as LDAP name to DN mapping:

  • previously, there had to be at least a single rule defined for mapping. When no mapping is defined, mapping fails. After this change, this requirement is lifted. User name would be considered to match LDAP DN
  • default user to DN mapping is an array containing a transform which converts user name to DN as-is. This change removes such default, and a new default is an empty array.

Description of Linked Ticket

Currently the userToDNMapper class requires at least one transform rule to function correctly.

Treat empty string (or `[]` / array) as performing no transformations without error.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 21/May/21 ]

Author:

{'name': 'andf-mongodb', 'email': 'andrew.feierabend@mongodb.com', 'username': 'andf-mongodb'}

Message: DOCS-14151 usertodnmapping default to username transform
Branch: v5.0
https://github.com/mongodb/docs/commit/b963a2de42281c5433a07173487a6014bc9a258a

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