- Notes, cautions, and warnings
- Disclaimer
- Preface
- Introduction
- Authentication
- Component access control
- Log in to PowerProtect Data Manager
- User and credential management
- Login security settings
- Authentication types and setup
- Identity providers
- Authentication to external systems
- Authorization
- Log Settings
- Network and Communication Security Settings
- Data Security Settings
- Cryptography
- Security Updates and Patching
- Authenticity and Integrity
- About product authenticity and integrity
- Verification
- Verify the signer or signers for Windows binaries
- Verify the vendor for Linux (RPM-based) packages
- Verify the vendor for Linux (Debian-based) packages
- Verify GPG signatures for Linux (RPM-based) packages
- Verify the signature for JAR files
- Verify SHA-256 checksums in Windows
- Verify SHA-256 checksums in Linux
- Verify SHA-256 checksums in AIX
- Miscellaneous Configuration and Management Elements
- REST API Procedures
PowerProtect Data Manager 19.10 Security Configuration Guide
Operating system expired password impacts
For the Linux operating system admin and root user passwords, some aspects of PowerProtect Data Manager may not operate correctly when one or both passwords expire.
Protection engine and Search Engine node operating system passwords do not expire. PowerProtect Data Manager automatically manages these passwords, which are meant for system use only.
All functionality that is not listed in these sections continues to work after passwords expire.
Admin password expires
- Software update prechecks fail and block the update process.
- The server DR service script must be run by the root user. Running the script as the root user changes the service script ownership and the ownership of related files to the root user.
Root password expires
- The system manager cannot start after PowerProtect Data Manager restarts. System operations that require root privileges fail. For example, changing expirations, opening network ports, and changes to file ownership.
- Software update prechecks fail and block the update process.
- sudo operations for server DR, such as mounting, unmounting, and permissions or ownership changes fail and block related operations, including:
- Changing the server DR storage target from NFS to DD Boost, or from DD Boost to NFS.
- Changing the server DR storage target from one protection storage system to another.
- Password synchronization with the storage target.
- Server DR restores.
- The compliance verification Docker service and compliance verification services cannot start.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\