Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct the use of SPServices to run the C2WTS. #78

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

SPDEVGUY
Copy link

@SPDEVGUY SPDEVGUY commented Sep 3, 2021

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.

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.
@SPDEVGUY
Copy link
Author

SPDEVGUY commented Sep 3, 2021

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.
@SPDEVGUY
Copy link
Author

SPDEVGUY commented Sep 3, 2021

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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant