PTS_ADDUSER(1)

📦
version 1.8.16.1 · 10 versions
, in ubuntu stonking

✨ PTS_ADDUSER(1) ✨

okay bestie, welcome to pts_adduser — the AFS Command Reference glow-up edition 🎀 (yes it lives in the pts family, section 1, we love a classic)

💖 NAME 💖

pts_adduser — adds a user or machine to a Protection Database group. literally that's the whole job and she does it flawlessly 💅

🌸 SYNOPSIS 🌸

pts adduser -user <user name>+ -group <group name>+
    [-cell <cell name>] [-noauth] [-localauth] [-force] [-help]
    [-auth] [-encrypt] [-config <config directory>]

pts ad -u <user name>+ -g <group name>+
    [-c <cell name>] [-n] [-l] [-f] [-h]
    [-a] [-e] [-co <config directory>]
not the short-form era too bestie 😭 pts ad is the same command in its little abbreviation fit, and -u, -g, -c, -n, -l, -f, -h, -a, -e, -co are just the glow-down versions of the long flags. iconic behavior honestly.

🦋 DESCRIPTION 🦋

The pts adduser command adds each user or machine entry named by the -user argument as a member of each group named by the -group argument. like, everyone in the first list joins every group in the second list. it's a whole "you're ALL invited" scenario 💌

Wanna kick people out instead? use the pts removeuser command, bestie. Wanna see which groups a user or machine belongs to, or who's inside a specific group? that's the pts membership command, chef's kiss ✨

🚨 CAUTIONS 🚨

Real talk, this one matters: after being added as a group member, a currently authenticated user must reauthenticate (for example, by issuing the aklog or klog.krb5 commands) to obtain permissions granted to the group on an access control list (ACL).

ngl this is the classic "why don't my perms work" moment 😭 your token is still wearing its old outfit. reauth and she'll show up to the group chat properly 💅

🌈 OPTIONS 🌈

  • -user <user name>+ — Specifies the name of each user or machine entry to add to each group named by the -group argument. The name of a machine entry resembles an IP address and can use the wildcard notation described on the pts createuser reference page. The user or machine entry must already exist in the Protection Database — no spontaneous arrivals, sorry 🫶
  • -group <group name>+ — Specifies the complete name (including the owner prefix if applicable) of each group to which to add members. The group entry must already exist in the Protection Database. yes bestie, the owner prefix is part of the vibe, don't skip it ✨
  • -auth — Use the calling user's tokens to communicate with the Protection Server. For more details, see pts(1). your tokens, your power 👑
  • -cell <cell name> — Names the cell in which to run the command. For more details, see pts(1).
  • -config <config directory> — Use an alternate config directory. For more details, see pts(1).
  • -encrypt — Encrypts any communication with the Protection Server. For more details, see pts(1). keep those messages on lock 🔒
  • -force — Enables the command to continue executing as far as possible when errors or other problems occur, rather than halting execution at the first error. she's not gonna stop the party for one little oops 💪
  • -help — Prints the online help for this command. All other valid options are ignored. she said "help first, everything else later" 🙈
  • -localauth — Constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. Do not combine this flag with the -cell or -noauth options. For more details, see pts(1). read that again bestie, no mixing 🚫
  • -noauth — Assigns the unprivileged identity anonymous to the issuer. For more details, see pts(1). it's giving "who dis" energy 💀

🍓 EXAMPLES 🍓

The following example adds user smith to the group system:administrators.

% pts adduser -user smith -group system:administrators

The following example adds users "jones", "terry", and pat to the smith:colleagues group.

% pts adduser -user jones terry pat -group smith:colleagues

The following example adds the machine entries in the Example Corporation subnet to the group "bin-prot". Because of the IP address range of the Example Corporation subnet, the system administrator was able to group the machines into three machine entries (using the wildcard notation discussed on the pts createuser reference page).

% pts adduser -user 138.255.0.0 192.12.105.0 192.12.106.0 -group bin-prot
three entries for a whole subnet? efficiency queen 👑 she understood the assignment.

👑 PRIVILEGE REQUIRED 👑

The required privilege depends on the setting of the fourth privacy flag in the Protection Database entry for each group named by the -group argument (use the pts examine command to display the flags):

  • If it is the hyphen, only the group's owner and members of the system:administrators group can add members.
  • If it is lowercase "a", current members of the group can add new members.
  • If it is uppercase "A", anyone who can access the cell's database server machines can add new members.

so yeah, go stare at that fourth flag before you start acting up 💅

🔥 SEE ALSO 🔥

pts(1), pts_createuser(1), pts_examine(1), pts_membership(1), pts_removeuser(1), pts_setfields(1)

IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.

This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.

and that's the page bestie 🫶 brought to you by OpenAFS, dated 2026-07-27, filed under PTS_ADDUSER(1) — now go add someone to a group and slay ✨🎀

📦 where this page comes from