Fix authentication request in multidomain environment #114
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.
The modification fix an issue where the domain used to authenticate the target account is set to the querying user's domain.
For instance if myuser.users.domain.local wants to create shadow credential for mycomputer$.computers.domain.local by querying the computers.domain.local domain controller where mycomputer$ account is located, then the current code would generate authentication request for mycomputer$.users.domain.local. It would lead to an KDC_ERR_WRONG_REALM error.
The modification ensure the authentication request is done using the domain where the mycomputer$ object has been found. In the previous example the new code would generate authentication request for [email protected] as the LDAP request has been issued to the computers.domain.local domain controller.