Skip to content

extended: wrap requestValue as RFC 4511 [1] OCTET STRING - #628

Open
team-humaki wants to merge 1 commit into
go-ldap:masterfrom
team-humaki:extended-request-value-octet-string
Open

team-humaki wants to merge 1 commit into
go-ldap:masterfrom
team-humaki:extended-request-value-octet-string

Conversation

@team-humaki

Copy link
Copy Markdown

RFC 4511 encodes requestValue as context-specific [1] OCTET STRING. ExtendedRequest.appendTo was appending the caller BER payload as a bare child, so NMAS/eDirectory rejected a request that OpenLDAP accepted (NMAS Extension invalid version).

Wrap unwrapped payloads as [1] OCTET STRING holding the serialized BER. Leave packets that are already context class tag 1 unchanged so Password Modify-style callers are not double-wrapped.

Fixes #627

appendTo appended the caller BER payload as a bare child of
ExtendedRequest, so NMAS/eDirectory rejected the request as
"invalid version". Encode requestValue as context-specific tag 1
OCTET STRING holding the serialized payload. Leave packets that
are already [1] unchanged so Password Modify-style callers are
not double-wrapped.

Fixes go-ldap#627

Signed-off-by: Team Humaki <team@humaki.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ExtendedRequest returns NMAS error (-1652) while equivalent OpenLDAP C implementation succeeds against eDirectory Universal Password OID

1 participant