Overview
Managing passwords for test accounts can be time-consuming, especially when dealing with large volumes of accounts or when security policies require frequent updates. This article guides two methods for updating passwords: Bulk Account Creation and API Account Management. Each method has its advantages and is suited to different environments, depending on factors such as account naming conventions and password policies.
Bulk Account Creation
Bulk account creation works well when the following conditions are met:
- All users follow the same naming convention (e.g., Testuserxxxx).
- All users have the same password.
However, this method may not be ideal if you require unique passwords or frequent password changes.
API Account Management
You can find API details at <Your VA Appliance>/publicApi/v6-preview/docs/index.html
Using our API, you can integrate password updates in various ways. For instance, you can create a PowerShell script to add a new account.
For complete examples, refer to the attached files. They include a scenario where an account true-up script will update a password or create a new account as needed. Note that you must populate the password.csv file with test accounts and update lines 5-7 in the script with your environment-specific values.
- Line 5: Update with the path to your Login Enterprise Appliance.
- Line 6: Update with a token, which can be created under the Login Enterprise sidebar menu > External Notifications > Public API.
- Line 7: Update with the location of the password.csv file you are importing.
- password.csv122 Bytes
- accounttrueup.ps15 KB