From: Nico Cesar Date: Mon, 15 Feb 2021 20:44:50 +0000 (-0500) Subject: Added note about /bin/false as UNIX login X-Git-Tag: 2.2.0~123^2 X-Git-Url: https://git.arvados.org/arvados.git/commitdiff_plain/b5884b515a7fe6255761020cdd39d450db6d603b Added note about /bin/false as UNIX login Arvados-DCO-1.1-Signed-off-by: Nico Cesar --- diff --git a/doc/install/setup-login.html.textile.liquid b/doc/install/setup-login.html.textile.liquid index aec82cfe2a..d11fec9e10 100644 --- a/doc/install/setup-login.html.textile.liquid +++ b/doc/install/setup-login.html.textile.liquid @@ -98,7 +98,7 @@ Enable PAM authentication in @config.yml@: Check the "default config file":{{site.baseurl}}/admin/config.html for more PAM configuration options. -The default PAM configuration on most Linux systems uses the local password database in @/etc/shadow@ for all logins. In this case, in order to log in to Arvados, users must have a shell account and password on the controller host itself. This can be convenient for a single-user or test cluster. +The default PAM configuration on most Linux systems uses the local password database in @/etc/shadow@ for all logins. In this case, in order to log in to Arvados, users must have a UNIX account and password on the controller host itself. This can be convenient for a single-user or test cluster. User accounts can have @/dev/false@ as the shell in order to allow the user to log into Arvados but not log into a shell on the controller host. PAM can also be configured to use different backends like LDAP. In a production environment, PAM configuration should use the service name ("arvados" by default) to set a separate policy for Arvados logins: generally, Arvados users should not have shell accounts on the controller node.