Technical Article for Creating and Managing Users with a Bash Script

Margret Mary — Tue, 02 Jul 2024 17:25:43 +0000

This article describes a Bash script, create_users.sh, designed to automate the creation of user accounts and group assignments based on a text file containing user data. This script streamlines the user onboarding process for system administrators, improving efficiency and reducing the risk of errors.

Script Functionality:

The script takes a text file as input, where each line represents a user with the following format:

username;groups
username: The desired username for the new account.
groups: A comma-separated list of groups the user should belong to.

Here's a breakdown of the script's functionality:

Reads User List: The script iterates through each line of the provided text file.
Processes User and Groups: It extracts the username and groups (if any) from each line.
Creates User and Primary Group: The script creates a primary group with the same name as the username and adds the user to it.
Error Handling: It checks if the user already exists. If so, it logs a warning message and skips to the next user.
Generates Random Password: A secure, random password is generated for each user.
Creates Home Directory: The script creates a home directory for the new user and sets appropriate ownership and permissions.
Sets User Password: The script securely sets the generated password for the user account.
Adds User to Additional Groups: If additional groups are specified in the input file, the script adds the user to those groups.
Logs Activity: All actions (user creation, group assignment, etc.) are logged to a dedicated log file for audit purposes.
Stores Passwords Securely: Passwords are not stored directly in the script or logs. Instead, they are saved in a separate file with restricted permissions (accessible only by the script user).

Technical Details:

The script utilizes various Linux commands to achieve its functionalities. Here's a brief overview of some key commands:

useradd: Creates a new user account.
groupadd: Creates a new group.
chpasswd: Sets or modifies a user's password.
/dev/urandom: Generates random data from the system's random number generator.
tr: Transforms characters (used for filtering random data to alphanumeric characters).
usermod: Modifies an existing user account.

Benefits of Script Automation:

Using a script to automate user creation offers several benefits:

Efficiency: It significantly reduces the time and effort required to create multiple user accounts.
Accuracy: Automating the process minimizes the risk of typos or errors that can occur during manual user creation.
Consistency: The script ensures that all user accounts are created with the same settings and permissions, promoting consistency across the system.
Auditability: The logging mechanism provides a clear record of all user creation activities, useful for security purposes and troubleshooting.

Conclusion

By following these steps, we can automate the user creation process, ensuring consistency and saving time. This approach can be easily extended or modified to fit specific requirements.

For more information on our internship program, visit HNG Internship and Start your journey to becoming a world-class developer today, check out HNG.

Unearthing Efficiency: My Experience Bug Hunting with SAW

Margret Mary — Tue, 02 Jul 2024 14:13:56 +0000

Scrape Any Website (SAW) promises to be a powerful tool for web data extraction. But as with any software, a keen eye can uncover areas for improvement. This blog post details my exploration of SAW, highlighting the bugs I encountered and suggesting potential solutions.

Exploratory Testing: Delving into SAW's Functionalities

My journey began with downloading SAW from the official Windows Store download page SAW - Windows Store. Launching the application, I familiarized myself with the interface, focusing on testing various features and pushing the app to its limits. My goal was to identify not just bugs, but also areas where usability could be enhanced.
Bug Report: Unveiling the Cracks in the Facade

My exploration yielded several noteworthy bugs. Here are a few of the most critical ones:

Missing Selectivity: Let's say you only want to scrape data from a specific web page. Unfortunately, the current version of SAW doesn't allow you to select individual URLs for scraping. Instead, it scrapes all URLs associated with a website. This can be a major roadblock if you're only interested in a specific data set.

Unresponsive UI Elements : Hovering over the some options resulted in no visual change, unlike other interactive elements. This inconsistency can lead to user confusion, making it unclear if the option is functional. Implementing consistent hover effects would improve the user experience.

Inoperable Settings: The settings menu within SAW offered configuration options for browsers, but lacked a crucial "Save" button. Without this functionality, any adjustments made are lost upon closing the application. A prominent "Save" button is essential to ensure user-defined settings persist.

Dashboard Disconnect: The main dashboard seems to be grappling with a communication gap. Jobs and URLs added to scrape jobs don't always reflect on the dashboard, leaving you uncertain about the progress or presence of your data.

Information Blackout: Obtaining basic information about the software itself, like the version number, proved to be a challenge. Additionally, there's no built-in help section or FAQ to guide users through potential issues.

Beyond Bug Hunting: Suggestions for Improvement

While bug fixing is vital, I believe SAW has the potential to be even more user-friendly. Here are some additional suggestions:

Informative Dashboard: The main dashboard currently displays limited information. Highlighting the number of URLs added, scrape status, and extracted data would provide valuable insights at a glance.

Accessibility Features: Integrating features like software version information and a dedicated Help section with FAQs would empower users to troubleshoot independently and stay informed.

Granular URL Selection: The ability to choose specific URLs within a scrape job would empower users to target their data collection precisely.
Enhanced User Interface: Incorporating hover highlights and other visual cues can significantly improve the application's user-friendliness and intuitiveness.

Real-Time Dashboard Updates: A dynamic and responsive dashboard that reflects changes made within the application would provide valuable feedback to users and eliminate confusion.

Conclusion: A Work in Progress

SAW presents a promising solution for web data extraction. By addressing the identified bugs and incorporating the suggested improvements, SAW can evolve into a powerful and user-friendly tool. This experience has solidified the importance of thorough testing in software development. For a detailed exploration of the bugs I encountered, you can access my comprehensive bug report SAW BUG Report.xlsx. Additionally, to download SAW and embark on your own data scraping adventures, visit the official Scrape Any Website or the Windows Store.

DEV Community: Margret Mary