Local Users

Learn about configurations >

• allow-existing-users | boolean

  When set to False the charm will enter 'blocked' state when user exists in 'users' config and in the system, but not in the charm managed group. Setting to True disables that protection and allows for pre-existing users to be added to the charm managed group.

• backup-path | string

  Default: /var/lib/misc/charm-local-users/backup

  Location on the unit that will be used for storing backups of home directories of removed users.

• group | string

  Default: charm-managed

  Group name for users managed by the charm.

• ssh-authorized-keys | string

  Default: $HOME/.ssh/authorized_keys

  The file to write the SSH public keys to. This option supports the usage of variables "$USER", "$HOME" and "$UID" in the path string. They will be expanded to the username, home directory and the user id of each user.

• sudoers | string

  Custom /etc/sudoers.d file. File name is 70-local-users-charm Visudo is used to check for syntax errors and print them in the charm status and more verbose in juju debug logs.

  Example: Cmnd_Alias ALLOWED_CMDS = /usr/sbin/dmidecode,
  /usr/sbin/hwinfo,
  /sbin/ifconfig,
  /bin/ps

  myuser ALL = (ALL) NOPASSWD: ALLOWED_CMDS

• users | string

  List of (username; Gecos Name; SSH pub key) tuples. Fields must be separated by semicolons ';'. Multiple ssh keys can be provided per user by adding multiple lines with the same username and gecos. SSH keys can also be retrieved from launchpad by using the launchpad username prepended with 'lp:'

  Example: alice;Alice;<ssh_pub_key> bob;Bob;<ssh_pub_key> alice;Alice;lp:alice bob;Bob;lp:bob monitoring;Remote Monitoring;<ssh_pub_key1> monitoring;Remote Monitoring;<ssh_pub_key2> monitoring;Remote Monitoring;<ssh_pub_key3>