Versions Compared
compared with
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Comment:
Rebranding rollback.
In an emergency, if the Axidian Privilege Indeed Identity PAM components fail, you can dump the privileged account passwords from the Axidian Privilege Indeed Identity PAM database.
Location of dump utility indeed-pam-windows\MISC\Dump\Pam.Tools.Dump.exe
At first, Open the utility config file indeed-pam-windows\MISC\Dump\appsettings.json and specify the access parameters for the Core database:
Database section
- Database — DBMS provider
- mssql — Microsoft SQL Server
- pgsql — PostgreSQL, PostgreSQL Pro
ConnectionStrings
| Divbox | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Divbox | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Encryption section
- Algorithm — Core database encryption algorithm
- Key — Core database encryption key
The utility can be executed with the following arguments:
- sshKey — dumping the SSH key of a privileged account, you must specify the account, for example:
Pam.Tools.Dump.exe sshKey --name res2\administrator - password — dumping the password of a privileged account, you must specify an account, for example:
Pam.Tools.Dump.exe password --name res2\administrator - secrets — dumping all credentials to the .\Results folder, or to the specified one. Passwords will be dumped to accounts.csv file, keys will be dumped to sshKeys folder in separate files. Example command:
Pam.Tools.Dump.exe secrets --output c:\temp - help — shows help contents