Creating and Updating ACM Accounts¶
Users¶
Create a New User¶
User creation is mostly automated by file:///afs/acm.jhu.edu/readonly/group/admins.pub/scripts/newuser . Invoke it as
/afs/acm.jhu.edu/readonly/group/admins.pub/scripts/newuser ${NEW_USER_NAME}
The remaining steps involve using the LDAP tools to find a new UID and create a new user account.
Create a New Cross-Realm User¶
While this will happen automagically when the user aklogs to the new/our realm, sometimes it’s nice to do things ahead of time:
pts createuser ${user_name}@${realm_name}
should suffice!
Changing a User’s Username¶
Until changeuser is written, apparently you can do the following if you need/want to change a username. At least according to this username-change file I found in the old notes…
- Rename kerberos principles (renprinc OLD NEW in kadmin; for their base and all other hats)
- modrdn the users’s LDAP object and change attributes referring to username; change any from other LDAP objects
- rename PTS hats (pts rename; check for other hats for groups owned by user)
- rename AFS volumes
- rename AFS mountpoints (in …/user and …/readonly/user; release volumes containing those)
- Looking through newuser, there appears to be nothing else that needs changing…hope it works out?
Groups¶
Create a New Group¶
Group creation is entirely automated by file:///afs/acm.jhu.edu/readonly/group/admins.pub/scripts/new-afs-group . Invoke it as
/afs/acm.jhu.edu/readonly/group/admins.pub/scripts/new-afs-group ${NEW_GROUP_NAME}
This script creates both org:${NEW_GROUP_NAME} and
org:${NEW_GROUP_NAME}-admins in PTS and tries to set the permissions
“cleverly”. It then creates both a group and a group-scratch volume, makes the
mountpoints, and releases all volumes involved.
AFS Groups discusses the PTS group game from the end-users’ perspective.
Create a New Mailing List¶
Todo
This is not yet documented.