Active Directory fixes for alternate encoding RFC4514 #324
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As part of RFC4514 section 2.4, it's permissible to prefix some characters with the backslash (
\
) symbol instead of using the standard format of\xx
wherexx
is the hexadecimal code for the character in question. This was exposed when a group in Active Directory (AD) was created with a#
symbol.Consider the DN
CN=#Supers,DC=foo,DC=bar,DC=com
. AD sends this asCN=\#Supers,DC=foo,DC=bar,DC=com
, which is an alternative format according to the spec. However the#
symbol is hex code 23. This mean the standardized form via the spec should result inCN=\23Supers,DC=foo,DC=bar,DC=com
. Unfortunately during testing AD will return the record, if and only if, the alternative format is used.The relevant section of the RFC for this change follows