The AuthAnvil Password Server Vault Import script allows you to import a large quantity of Scopes, Vaults, and Passwords simultaneously without having to manually click through every step.
Bulk Vault Import Script for v1.6 and newer & v1.5 are attached to the Article. PWS v1.7 and later include native features for importing data.
These scripts allow you to import a large quantity of Scopes -> Vaults -> Passwords into your AuthAnvil Password Server based on folders and password import files (.csv). This is a Command Line PowerShell 2.0 script (ZIP package).
- This script must be run on the machine where AAPS is installed.
- The AAPSServiceClient DLL must be in the same location as this script.
- A Third Party Certificate file ("ThirdPartyCert.pfx" by default) must be generated on the "External Settings" page in AAPS and downloaded to the same location as this script.
- A directory named "data" must be in the same location as this script.
- Create separate directories in "data" with names matching new or existing Scopes in AAPS.
- Add properly formatted Password Import CSV files to those Scope directories with filenames matching new or existing Vaults within those Scopes.
Note: If your passwords, vaults, or scopes have names or values that have invalid characters they will fail to be created. All entries within that scope / vault password import file will be skipped.
- Run "AAPSVaultImport.ps1" in PowerShell.
- If AAPS contains more than one Organization, select your Organization from the outputted list.
- Enter the logon credentials for an AAPS user with Administrator permissions for that Organization.
Provided that the logon credentials are valid, the script will then do the following:
1. For each directory inside "data":
1.1. Check if a Scope of the same name already exists in that Organization.
- If not, then create a new Scope with that name and continue.
1.2. Create a new role mapped to the Scope and assign the running user to that role
1.3. For each CSV file inside the Scope directory:
1.3.1. Check if a Vault of the same name already exists in that Scope.
-If not, then create a new Vault in that Scope
-Vault will use server default Password Policy
1.3.2. Import the CSV file of Passwords into that Vault
-If a Password in the CSV file has the same name as an existing Password in that Vault, then that Password will be ignored.
-If a Password in the CSV file does not meet the vault password policy the
Note: A "data" directory containing sample Scopes, Vaults, and Passwords is included with this download.
Note: This import process is not currently supported using Password Server v2.5 - newer.
If you have any questions or need some help, we would be happy to assist. Open a case at kaseya.zendesk.com .