You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A DN may contain RDNs that are separated by semi colons. Looks like the current code doesn't handle this correctly.
I believe this can be fixed by changing the following lines in Dn.parseDn method:
Line 104 from: case char == ',' || char == '+':
to: case char == ',' || char == '+' || char == ';':
Line 112 from: if char == ',' {
to: if char == ',' || char == ';' {
The text was updated successfully, but these errors were encountered:
Relationship with RFC 1779 and LDAPv2
[...]
Implementations MUST allow a semicolon character to be used instead
of a comma to separate RDNs in a distinguished name, and MUST also
allow whitespace characters to be present on either side of the comma
or semicolon. The whitespace characters are ignored, and the
semicolon replaced with a comma.
A DN may contain RDNs that are separated by semi colons. Looks like the current code doesn't handle this correctly.
I believe this can be fixed by changing the following lines in Dn.parseDn method:
Line 104 from:
case char == ',' || char == '+':
to:
case char == ',' || char == '+' || char == ';':
Line 112 from:
if char == ',' {
to:
if char == ',' || char == ';' {
The text was updated successfully, but these errors were encountered: