Correct the use of SPServices to run the C2WTS. #78
Conversation
This file contains hidden or 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
The SPServices account is not the right account to be running the claims to windows token service as. The C2WTS account requires very special elevated permissions and adding the Services account to local admins will result in warnings displayed in the health analyzer. Unfortunately I don't yet know how to automate configuring of local security policies as it is very low level from what I can google currently... however this is a much better step in the right direction of informing the user they need a specific account with very high risk permissions.
|
Note - I didn't update the configuration file version but it will be needed. I assume this is usually part of your own process of merging and compiling updates. |
If your WFE is named "NMS-UAT" and your APP is named "NMS-UATAPP" the MatchComputerName will incorrectly return true and cause the service provisioning to try and provision a service from another machine on the current machine. This specifically was happening with the ClaimsToWindowsToken service.
|
Also potentially included a fix for #77 as it was caused by MatchComputerName |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 SPServices account is not the right account to be running the claims to windows token service as. The C2WTS account requires very special elevated permissions and adding the Services account to local admins will result in warnings displayed in the health analyzer. Unfortunately I don't yet know how to automate configuring of local security policies as it is very low level from what I can google currently... however this is a much better step in the right direction of informing the user they need a specific account with very high risk permissions.