Skip to content

Conversation

Rican7
Copy link
Contributor

@Rican7 Rican7 commented Nov 16, 2015

This PR fixes the fall-back order of the authentication message encoder's target name acquisition to allow for client overriding.

Or in other words, code that called NtlmV1AuthenticateMessageEncoder::encode() and/or NtlmV2AuthenticateMessageEncoder:encode() were unable to present a manual NT-domain/target-name, as the implementations were always taking the server's challenge message target-name as truth.

The reliance on the server challenge makes sense in a lot of cases, and still does if a user calls these methods with empty values, however it disallowed any sort of manual entry which is necessary in some multi-tenant service authentication environments.

message encoder's target name to allow for client overriding
@Rican7 Rican7 added the bug label Nov 16, 2015
@brianmuse
Copy link
Member

👍 LGTM

@jstruzik
Copy link
Contributor

👍

jstruzik added a commit that referenced this pull request Nov 16, 2015
@jstruzik jstruzik merged commit 38082f9 into robinpowered:master Nov 16, 2015
@Rican7 Rican7 deleted the bugfix/target-name-overriding branch November 16, 2015 22:23
@Rican7
Copy link
Contributor Author

Rican7 commented Nov 16, 2015

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants