From a812c840d35cb34380d1eaeed9d5a2567fd5b321 Mon Sep 17 00:00:00 2001 From: Konrad Bucheli Date: Fri, 6 Mar 2026 11:59:11 +0100 Subject: [PATCH] document systemd linger --- .../configuration/access/service_user.md | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 docs/admin-guide/configuration/access/service_user.md diff --git a/docs/admin-guide/configuration/access/service_user.md b/docs/admin-guide/configuration/access/service_user.md new file mode 100644 index 00000000..758cb5fc --- /dev/null +++ b/docs/admin-guide/configuration/access/service_user.md @@ -0,0 +1,21 @@ +# Service User/Account + +A service user is used for running a software daemon or backend with an own identity. +Especially if it needs to communicate with central infrastrucure or needs to share data with other systems (NFS storage), then it is useful if it is defined in the ActiveDirectory (AD). +The service user can then also be part of AD groups to allow access required data. + +The usus is that the login name of service user starts with `svcusr-`, followed by the naming identifier. +It can be ordered with a [free text request in Service Now](https://psi.service-now.com/psisp?id=psi_report_new_incident&sys_id=797c79ebdbf20454d648f90532961982). + +# Automatic Kerberos +The `gssproxy` service provides transparend authentication for accessing Kerberos protected NFS or CIFS shares. +The guide [Permanent Kerberos with gssproxy and Password Keytab](https://linux.psi.ch/documentation/admin-guide/configuration/basic/gssproxy_with_keytab/) shows how to get there. + +# Create Systemd Session at Boot (Systemd Linger) +If that user needs a full Systemd session, i.e. a own `systemd --user` instance already started at boot, you can configure it in Hiera: + +``` +systemd::linger_users: + - svcusr-lx_test +``` +