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

Registering task with non-service account not working #14

Open
ArwynFr opened this issue May 1, 2023 · 1 comment
Open

Registering task with non-service account not working #14

ArwynFr opened this issue May 1, 2023 · 1 comment
Assignees
Labels

Comments

@ArwynFr
Copy link
Member

ArwynFr commented May 1, 2023

Usage of Register-ArmaServerTask with -UserId xxx is not working.

For details, see: https://stackoverflow.com/a/70793765/6092856

@ArwynFr
Copy link
Member Author

ArwynFr commented May 2, 2023

We should use different principals for the scheduled task and running the game.

The scheduled task needs write access over steamcmd for autoupdate and allow login as batch job.
This could run under the current user's principal unless another account is specified (it should not be LocalService).
It also needs:

  • Read access to the server configuration file, pid files, and the STEAM_USERNAME environment variable
  • Write access to workshop content, master, config and transcript logs

The game should run as LocalService with as few privileges as possible. It needs:

  • Read access to workshop content, master, config
  • Write acess to pid files and profile directory

As a consequence, pid fils should not go in the config directory, and transcripts should not go in the profile path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant