- play_arrow Introduction
- play_arrow Overview
- play_arrow Access and Manage Paragon Automation Account
-
- play_arrow Device Life Cycle Management
- play_arrow Introduction
- play_arrow Day-Wise Activities for Device Life Cycle Management
- play_arrow Field Technician User Interface
- play_arrow Onboarding Profiles
- play_arrow Plan Device Onboarding
- play_arrow View Device Onboarding
- play_arrow Device Management
- Device Management Workflow
- Device Licenses Overview
- About the Features Tab
- About the Licenses Tab
- Manage Device Licenses
- About the Software Images Page
- Upload a Software Image
- Delete a Software Image
- About the Configuration Backups Page
- Configuration Templates Overview
- About the Configuration Templates Page
- Add a Configuration Template
- Edit and Delete a Configuration Template
- Preview a Configuration Template
- Deploy a Configuration Template to a Device
-
- play_arrow Observability
- play_arrow Introduction
- play_arrow Troubleshoot Devices
- play_arrow View Network Topology
-
- play_arrow Trust and Compliance
- play_arrow Introduction
- play_arrow Manage Trust Settings and Trust Scores
- Compliance Standards Overview
- About the Compliance Benchmarks Page
- About the Compliance Tailorings Page
- Example: Create a Tailoring Document for NTP Settings
- About the Compliance Checklist Page
- Add a Checklist Template
- Add Checklist for a Device
- Import Scans and Update Rule Results in a Checklist
- Trust Plans Overview
- About the Network Score Formula Page
- Trust Score Overview
- About the Network Score Page
- About the Snapshots Page
- Add a Snapshot for a Target
- play_arrow Manage Compliance Scans
- play_arrow Manage Vulnerabilities
- play_arrow Monitor Integrity
-
- play_arrow Service Orchestration
- play_arrow Introduction
- play_arrow View Service Design Catalog
- play_arrow Manage Customers
- play_arrow Add Resources for Network Services
- play_arrow Manage Service Instances
- play_arrow Provision L3VPN Service
- play_arrow Monitor Service Order Execution Workflows
-
- play_arrow Active Assurance
- play_arrow Introduction
- play_arrow Test Agents
- play_arrow Tests and Monitors
-
- play_arrow Paragon Shell CLI Reference
- play_arrow Introduction
- play_arrow Operational Mode Commands
- file copy
- monitor
- request paragon backup
- request paragon cluster pods reset
- request paragon cluster upgrade
- request paragon config
- request paragon deploy
- request paragon deploy cluster
- request paragon destroy cluster
- request paragon fix-permission
- request paragon load
- request paragon repair-node
- request paragon replace-node
- request paragon restore
- request paragon running-config
- request paragon ssh
- request paragon ssh-key
- request paragon storage cleanup
- request paragon super-user password reset
- request system decrypt password
- request system reboot
- show configuration paragon cluster
- show host disk usage
- show paragon backup
- show paragon certificate expiry-date certificate-type
- show paragon cluster
- show paragon cluster details
- show paragon cluster namespaces
- show paragon cluster nodes
- show paragon cluster pods
- show paragon cluster pods namespace healthbot sort
- show paragon images version
- show paragon images version namespace
- show paragon pvc details
- show paragon version
- play_arrow Configuration Mode Commands
- delete paragon cluster
- load set
- set paragon cluster applications
- set paragon cluster common-services ingress
- set paragon cluster install
- set paragon cluster mail-server
- set paragon cluster nodes
- set paragon cluster ntp
- set paragon cluster papi
- set paragon cluster victoria-metrics
- set paragon monitoring
- set system login
- play_arrow Troubleshooting Commands
- Troubleshoot Using the Paragon Shell CLI Commands
- request support information
- request paragon troubleshooting information
- request paragon debug
- request paragon debug get-tsdb-data
- request paragon debug insights-kafka-data
- request paragon debug kafka
- request paragon debug logs
- request paragon debug logs namespace
- request paragon debug postgres
- request paragon debug redis
- play_arrow Service Orchestration
- About the Service Orchestration cMGD CLI
- set foghorn:core org-id
- set service design default version
- show service order status
- show service order as-json
- show service order as-yaml
- show service designs
- show device dependant configuration
- show insights configuration
- show configuration foghorn:customers
- request service project add
- request service orders sync
- request network resources load
- request service order upload
- request service order place
- request service order modify
- request service order delete
- request service order submit
- request service order provision
- request service design install
- request service design uninstall
-
Manage Paragon Shell Users
System administrators (root user) use Paragon Shell to add users so that these users can access and manage Paragon Automation cluster configurations. The users created in Paragon Shell and Paragon Automation Web GUI are not shared across the two user interfaces.
The following sections describe the user management tasks you can perform by using Paragon Shell.
User information configured on one node is deployed across all the nodes in the Paragon Automation cluster.
Create a User
System administrators and superusers can use Paragon Shell to create users who can access and manage the Paragon Automation cluster based on the privileges defined by the role assigned to them.
To create a user:
For every user created by using Paragon Shell, a Linux user with identical username, access privileges, and authentication method is created on every single node in the Paragon Automation cluster.
When a commit is initiated from one node (node A), commit is first attempted on the rest of the nodes (node B, C, D) before it is attempted on the node on which the commit was initiated (node A). In case the commit fails on any of the nodes, the changes committed is rolled back on the nodes on which commit succeeded.
Commit fails when multiple users make changes to the cluster configuration at the same time from different nodes. In such scenarios, we need to rollback all the committed changes on the other nodes and only commit changes from a single node to ensure that all the nodes in the cluster have the same configuration.
Modify User Information
System administrators and superuser can modify the access privileges of users and the authentication method used to authenticate the user.
To modify user details:
Logging in to Paragon Shell as a New User
The system administrator manually shares the IP address and credentials (username and password) with the users to access Paragon Shell.
To log in to Paragon Shell as a new user:
Retrieve User Information On a Recovered Node in the Paragon Automation Cluster
When a node is repaired and recovered in the Paragon Automation cluster the user configuration on the node is lost. Users will not be able to use their user credentials to log in to the node and access the Linux user shell and Paragon Shell.
Before you retrieve user configuration on the recovered node, ensure that there are no pending commits in any of the nodes in the Paragon Automation cluster, including in the recovered node.
To retrieve user configuration on the recovered node: