[SERVER-41347] Fix handling of non-strict arguments during option canonicalization Created: 28/May/19  Updated: 29/Oct/23  Resolved: 29/May/19

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

Type: Task Priority: Major - P3
Reporter: Sara Golemon Assignee: Sara Golemon
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Sprint: Security 2019-06-03
Participants:

 Description   

YAMLNodeToValue performs a canonicalization of the specified option while converting its value, however for "loose" option parsing, such as used by the mongo ldap tool, it's possible to receive no valid option from the canonicalization.  In this case, simply use the specified option name as-is.



 Comments   
Comment by Githook User [ 29/May/19 ]

Author:

{'email': 'sara.golemon@mongodb.com', 'name': 'Sara Golemon', 'username': 'sgolemon'}

Message: SERVER-41347 Fix handling of non-strict arguments during option canonicalization
Branch: master
https://github.com/mongodb/mongo/commit/e11c234484fe58681597ba74fd23fa76de734250

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