PDF Version Available
This document is also available in PDF format: usermgmt.pdf
The PDF version includes bookmarks for easy navigation and is optimized for printing.
Accessibility Notice
This document is also available in HTML format at:
Link: https://aholdengouveia.name/LinuxAdmin/labexcercises/usermgmt.html
The HTML version provides enhanced accessibility features including keyboard navigation, screen reader support, responsive design, dark mode support, and high contrast options.
Ticket
Ticket: ACME-2847
Requested by: HR
Systems: Both report servers
Background
HR has sent over a list of new hires, and one employee is leaving. Acme Corp needs a repeatable process for both, because this will happen every week. You will be working on the two servers you set up in the Server Setup lab: your Red Hat based server and your second server.
Learning Outcomes
By the end of this lab, you will be able to:
- Write scripts that add and remove user accounts from a list, including names that don't fit a standard format
- Manage groups, password rules, and admin rights using sudo
- Secure root access on a server
Requirements
- Write a script that creates accounts for everyone in the level 1 list of names (linked under Resources) on both servers. Choose a username format, and handle anything in the list that doesn't fit it.
- Run your script on the level 2 list of names.
- New users must change their password the first time they log in.
- Put users into department groups of your choice, and give one user admin rights using sudo, not root.
- Write an offboarding script for a departing user that locks the account, stops their running processes, and archives their home directory before the account is removed.
- Turn off direct root login over SSH.
Acceptance Criteria
- Everything must be cited. Every command, statement, and line of code in your scripts and documents must be cited, either with a link to a reference or with a note naming the previous class where you learned it, for example: # Learned in CIS 117 Intro to Linux. In scripts, put the citation in a comment next to the code. Anything without a citation will not count.
- Everything is tested on both servers.
- Screenshots show a new user logging in and being made to change their password, your sudo user using sudo, and a regular user being refused.
- Scripts are well commented and uploaded to GitHub.
- Every terminal screenshot shows your prompt with your username and hostname, and either the output of date or a note beside the terminal with your name and the term. Hostnames must match your server inventory from the Server Setup lab.
- Your GitHub repository shows your work over time: several commits across more than one day, each with a message describing the change, not a single upload of finished code.
Deliverables
Audience: the help desk team, who will use your process every time someone joins or leaves. Assume technical knowledge but not expertise. Screenshots are helpful to go with your descriptions.
Make sure your deliverables include documents for BOTH servers, clearly labeled with what the document is and which server it's for.
- Your onboarding and offboarding scripts, with a link to your GitHub where you've uploaded them.
- An onboarding and offboarding procedure document for the help desk.
- A short explanation of your username format, and how it handled the level 2 names.
- Your test screenshots.
Resources
References, a video, a PowerPoint and some notes are available at my website Link: https://www.aholdengouveia.name/LinuxAdmin/Usermgmt.html
Level 1 list of names Link: https://www.aholdengouveia.name/LinuxAdmin/UserNamesLvl1.txt
Level 2 list of names Link: https://www.aholdengouveia.name/LinuxAdmin/UserNamesLvl2.txt