NTLMv2 support for DOMAIN\UserName and username@domain.com username variations #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@gautamsi do you have an example, which value should I provide as target for |
|
Found it :) just empty string |
Closed
Closed
Fix bugs no longer crashes the process when url is invalid.
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
I wanted to use this package for NTLMv2 support in my repo
ews-javascript-api-auth. found out that domain\username format does not work in multiple domain forest. or even multiple forest scenario. upn format does not work either.figured that you have it hardcoded to domain/target returned from type2 message from server. With few tweaks it does work in both scenario. I have tested in cross forest scenario as well, both domain\username as well as username@domain.com works.