Updated --clientauth to use mspki-certificate-application-policy
instead of pKIExtendedKeyUsage
#14
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.
Repalced
pKIExtendedKeyUsage
withmspki-certificate-application-policy
for--clientauth
as it seems like the latter is what actually provides Domain authentication, and allows for the impersonation. Only adding Client Authentication to the pKIExtendedKeyUsage property ends up displaying an error when trying to Pass-The-Ticket with the resulting certificate:KDC_ERR_INCONSISTENT_KEY_PURPOSE
Error goes away and successfully passes the ticket (and authenticates) when adding Client Authentication to the mspki-certificate-application-policy property.