Enterprise Vault - Administration
- Quick start guide
- Administration application
- Recovery account
- Recovery data
- Synchronizing Trustelem Groups with the Enterprise Vault CLI (BETA)
Quick start guide
This quick start admin guide is divided into two parts.
First, the BUILD, which explains the operations to be carried out before starting to use the Enterprise Vault.
Secondly, the RUN, which lists the product life operations that can be performed.
BUILD
Enterprise Vault user creation and management uses WALLIX ONE IDaaS (also known as Trustelem), so the BUILD phase will involve configuring both Enterprise Vault and WALLIX ONE IDaaS.
1/ Subscription creation
When you subscribe to WALLIX ONE Enterprise Vault, you'll need to provide several pieces of information: among others the name of your company, and the names of future administrators.
Your company name will be used to create a WALLIX ONE IDaaS subscription.
For instance, MyCompany could have the subscription named "mycompany.trustelem.com".
The list of admins provided will be automatically provisioned when the subscription is created.
They will receive an email with :
- A link to initialize the account
- The subscription admin url (admin-your_name.trustelem.com) for WALLIX ONE IDaaS
- The subscription user url (your_name.trustelem.com) for WALLIX ONE IDaaS
- The link to the documentation
So, your first action as an administrator is to create your account using the link provided in the email, and then to go on the WALLIX ONE IDaaS administration page.
2/ Setup WALLIX ONE IDaaS
When you log on to the admin page, the subscription is empty, except for the first administrators. So you'll need to configure it.
There are 3 main things to do on WALLIX ONE IDaaS:
- Add Enterprise Vault applications
- Add users
- Give users access to Enterprise Vault
2.1/ Add Enterprise Vault applications
There are two applications to add:
- One for administrators, which includes auditing, logs and security policies.
Link to Enterprise Vault admin app documentation - The other for users, in which secrets are managed, as well as a few administrative tasks such as recovery.
Go to Apps, then Add an application, then select WALLIX Enterprise Vault and WALLIX Enterprise Vault administration.
2.2/ Add users
If you want to use directory or IDP users, you can do the following setup.
- Link to Active Directory documentation
- Link to Azure AD documentation
- Link to External IDP (Azure, Okta...) documentation
But if you want to use local users, you don't want to create them right away: they'll receive enrollment emails, while the rest of the setup isn't ready yet. That said, you can still create user groups, as they will be used for the next steps.
For instance, you can create a "Users" group, and an "Admins" group.
Go to Groups, then Create.
2.3/ Give users access to Enterprise Vault
You need to define who can access Enterprise Vault and how. To do this, you'll add permissions.
Permissions can be 1-factor, usually login and password, or two-factor with an additional secret.
Full documentation is available here:
Here's a summary of the main steps:
- Create permissions for users and administrators, usually in 2-factor mode.
Go to Access rules, select Create, then choose your apps et your groups
Internal & External zone depend of the users public IP which is compared to what is provided in Security > General > Internal network. - Enable the desired multi-factors in Security, Authentication factors, Login column
- In the same page, create an enrollment campaign to automate the 2nd factor enrollment
You'll probably want to use "enrollment during login", which allows the form to be displayed directly after authentication if the user doesn't yet have a 2nd factor.
3/ Setup Enterprise Vault admin application
The next step is to define Enterprise Vault administration policies.
Link to Enterprise Vault admin app documentation
Today there are 3 policies:
- Log: which information do you want to log?
- Recovery: do you allow master password reset ? Do you allow data recovery?
- Security: do you allow to list existing users in the forms that offer it in the user application?
If you want to use Recovery features, it is very important to enable it right now.
Indeed, if a user hasn't logged in AFTER you've activated the option, it won't be possible to help him if he loses his master password.
- Go to your user dashboard (your_name.trustelem.com) with an account that has access to the admin app
- Click the Admin app
- Go to Settings
- Enable the desired settings, then Save each categories
4/ Add the Enterprise Vault specific recovery rights for user
This step is only necessary if you want to use recovery.
There are 2 types of recovery:
- Account recovery, to manage master password reset requests
Link for account recovery documentation - Data recovery, to access a user's personal secrets.
Link for data recovery documentation
Each requires specific rights, which are controlled by WALLIX ONE IDaaS.
To carry out a data recovery action, a validation is required, with a quorum to be reached.
Defining quorum members also requires a specific right.
- Go to WALLIX ONE IDaaS admin dashboard, then click Users
- Select a User, click Edit and Add attribute
- For recovery account:
name: recovery_account
kind: bool
value: true - For recovery data:
name: recovery_data
kind: bool
value: true - For recovery data quorum:
name: recovery_data_workflow
kind: bool
value: true
Of course, recovery_data and recovery_data_workflow should never be assigned to the same person.
The first user with data/account recovery rights will automatically have the encryption keys needed for these operations. However, this will not be the case for subsequent administrators.
The first admin will have to share these keys via the recovery key sharing page on the user application.
(Settings > Recovery keys > Activate access)
Notes
- WALLIX ONE IDaaS administration page should always be secured using multi-factor authentication. To do so you need to enroll a 2nd factor for the admin accounts, then enable multi-factor using the option Authentication level for Trustelem admin console on Security settings > General.
- More information about WALLIX ONE IDaaS is available here: https://trustelem-doc.wallix.com/books/trustelem-administration
Now you're all set, you can create local users if you need to, and communicate about the availability of this new application.
RUN
Once Enterprise Vault is up and running, here's a list of the most important things administrators can do.
WALLIX ONE IDaaS
- Add / edit / delete users
- Change a user email on WALLIX ONE IDaaS will also change the email on Enterprise Vault.
- Deleting a user from WALLIX ONE IDaaS does not delete him from Enterprise Vault, but he will no longer be able to authenticate there.
- Re-creating a user identical to the one deleted will not allow data recovery from Enterprise Vault either: the 2 users will have different IDs. If you need to restore a user, you should use the Display recently deleted users option in the User list. - Unblocking a user
A user may have lost his first or second factor.
In both cases, you can unblock the user by clicking on his profile in the User list. - Add or remove Enterprise Vault rights to users
As explained above, on WALLIX ONE IDaaS you define the Enterprise Vault user rights: recovery_account, recovery_data or recovery_data_workflow. - View logs
On WALLIX ONE IDaaS, you can view all authentication-related information: when, who, what, how, from which IP, with which browser…
WALLIX Enterprise Vault admin app
Link to Enterprise Vault admin app documentation
- Audit Enterprise Vault usage
You can see how your users use the product via the Dashboard, Users and Shared Vault tabs. - Delete a user
In the Users tab, you can delete a user with his or her personal vault. - Force a change of master password or user encryption key
In the Users tab, you can force specific users to change their master password, with or without renewing their encryption keys. - Delete a shared vault
In the Shared Vault tab, you can delete a shared vault with all its objects. - View logs
In the Logs tab, you can audit all Enterprise Vault logged actions.
What is logged is defined in the log policy. - Change policies
In the Settings tab, you can modify your policies, particularly for recovery and logs.
WALLIX Enterprise Vault user app
- Validate a master password reset request
If a user has lost his master password and wishes to reset it, you must validate the request.
Link for account recovery documentation - Request access to a user's personal vault
If you wish to retrieve a secret that is no longer accessible due to the unavailability of its owner, you must make the request. Secrets will be accessible after approval by a quorum.
Link for data recovery documentation - Share recovery keys with a new admin
When a new admin has the recovery rights on WALLIX ONE IDaaS (recovery_data or recovery_account) it is not sufficient to perform recovery tasks. Indeed, another admin with access to the recovery keys must share them with the new admin first (Enterprise Vault user app > Settings > Recovery keys > Activate access).
Link for data recovery documentation or Link for account recovery documentation
Administration application
The Enterprise Vault admin application is dedicated to 5 usages :
- See Enterprise Vault usage
- Watch Enterprise Vault logs
- Define Enterprise Vault policies
- Manage Enterprise Vault existing users
- Manage Enterprise Vault existing shared vault
Do do so, you'll find 4 menus:
- Dashboard: a general overview of the existing vaults, with the clients used to access the secrets
- Users: information about the existing users (dates, vaults…)
- Shared Vault: information about the existing shared vault
- Logs: information about what happens on Enterprise Vault
- Settings: the global settings for Enterprise Vault
Dashboard
The dashboard tab displays a summary of the contents as well as the client interfaces used to access it.
This page gives a quick overview of Enterprise Vault adoption in your company. Among other things, you can see:
- Number of users (Personnal vaults > Vaults)
- Number of personal secrets (Personnal vaults > Items)
- Number of shared vaults (Shared vaults > Vaults)
- Number of shared secrets (Shared Vaults > Items)
- Type of client used (User interface)
There is one clickable information: the icon at the end of the user interface lines.
It gives details of the software used per user.
Users
The Users tab displays a list of WALLIX Enterprise Vault users. Users with anomalies are displayed in red.
This page shows, user by user:
- Creation, update and last access dates
- The number of personal secrets, as well as the number of personal folders and the number of existing sends
- The number of shared vaults where the user is owner or user
In addition, for each user it is possible to:
- Force a master password reset. In this case, the user must enter his old master password, then a new one.
- Force rotation of the user main encryption key, in addition to the master password reset.
- Delete the users and its secrets.
A user deleted on Enterprise Vault still exists on WALLIX ONE IDaaS.
Certain scenarios prevent the user from being deleted: for example, if the user is the only owner of the recovery key, or the only owner of a shared vault with members.
A user displayed in red has been deleted on the WALLIX ONE IDaaS side. But the user still exists on Enterprise Vault.
It is not possible to automate the user deletion on Enterprise Vault from WALLIX ONE IDaaS.
Shared Vault
This page shows, vault by vault:
- The creation date
- The active, unauthorized, deleted owners of the vault
- The active, unauthorized, deleted users of the vault
- The item and collection number
In addition, for each vault it is possible to delete the vault.
All owner/other member fields (active/unauthorized/deleted) are clickable, giving details of the users concerned.
Logs
The Logs tab displays the logs of actions performed and items viewed
This page shows:
- The creation date
- The user who performed the action
- Action category (administration, item, collection, shared vault, domain, recovery)
- Event corresponding to the action (User registration, Item creation, Item access...)
- The name of the shared vault associated with the item, if the action is relevant
- Additional data, such as the strength of the password created, or the IDs of objects affected by the action
There are 3 types of filters for searching logs, which can be combined:
- A text field, allowing you to enter any information you wish to search for on the page
- A records field, for filtering by category or event
- A date field, allowing you to select the range over which you wish to examine the logs.
At present, it is not possible to extract logs (export or link with SIEM).
Settings
The Settings tab allows the personnalisation of WALLIX Enterprise Vault according to your choices and security policies.
Today there are 3 policies:
- Log: which information do you want to log?
- Recovery: do you allow master password reset ? Do you allow data recovery?
- Security: do you allow to list existing users in the forms that offer it in the user application?
Log
- Log password access: define if password access are logged or not
If password access are logged, it is not possible anymore to have an offline access
- Log user actions client side: define if actions done on user client (browser/plugin...) are logged
- Log actions on user accounts: define if actions related to accounts (creation, deletion...) are logged
- Log actions on ciphers: define if actions related to encryption keys (creation, rotation...) are logged
- Log actions on collections: define if actions related to shared vault collections (creation, deletion...) are logged
- Log actions on shared vaults: define if actions related to share vaults (creation, changes, deletion...) are logged
- Log recovery actions: define if recovery actions (requests, validation, quorum...) are logged
Recovery
When recovery is enabled, each item will be encrypted with an additional key dedicated to recovery.
This encryption is added the first time the user decrypts his items with his own key.
Consequently, even if the recovery is enabled, these operations can only be performed AFTER the user has made a new access.
So if you want to use them, it's important to activate recovery features from the beginning!
Security
- Allow all users of a shared vault to be displayed: when you add new shared vault members, you have to provide a valid email address of an existing vault user. But if this option is enabled, you'll have the list of existing users instead.
Recovery account
Account recovery allows users to request a reset of their master password if they have lost it.
There are 3 prerequisites:
- Account recovery must be enabled in the administration page
- At least one user must have account recovery rights.
- The user must have a valid email address
The workflow will be as follows:
- User requests master password reset
- Admin accepts reset
- User sets new master password
Enable account recovery
- Go to the Enterprise Vault admin app
- Go to Settings
- Enable the line Authorize account recovery
- Click Save button
The length of time for which the request is valid can also be set here.
The default setting is 2 hours.
Add account recovery rights to a user
- Go to your WALLIX ONE IDaaS admin page
- Go to Users and select an existing user
- Click Edit then Add an attribute
- Provide the following attribute:
name: recovery_account
kind: bool
value: true
When this user will log in the Enterprise Vault user app, and if he is the first one with recovery rights(data or account), he will have the following message:
In fact, specific encryption keys are required to carry out recovery operations.
These are created when the first admin is authenticated.
Consequently, for subsequent admins, an admin who has the keys must share them.
- Go to your Enterprise Vault user app with an admin who has the recovery key
- Go to Settings, then Recovery keys
- Click Activate access for the new admins
Workflow
User requests master password reset
- Then he defines a reset code, which will be used later to complete the procedure
- Finally, he receives a confirmation email about his request
Admin accepts reset
- The admin is alerted by email
- He goes to his Enterprise Vault user app
- Then he clicks Recovery, an Approbation requests
- He can click Approve or Dismiss
User sets new master password
- When the master password reset request is validated, the user receive an email with a reset link
- He clicks the link, and arrives on the reset page
- He provides the initial reset code
- He can define the new master password
Recovery data
Data recovery allows admin to access personal items for selected users.
The point is to recover a secret which is no longer accessible due to the owner's unavailability.
Consequently, in this mode it is only possible to copy a personal secret's identifier, a personal secret's password, or to export the personal vault.
No other action is possible.
There are 4 prerequisites:
- Data recovery must be enabled in the administration page
- At least one user must have data recovery rights.
- At least one user must have the rights to manage data recovery quorum.
- The quorum must be defined.
The workflow will be as follows:
- An admin requests the access to a specific user account
- The quorum members are notified and accept the request
- The admin is notified and reload his user app: he has access to the user personal items
Enable Data recovery
- Go to the Enterprise Vault admin app
- Go to Settings
- Enable the line Authorize data recovery
- Click Save button
The length of time for which the request is valid when accepted can also be set here.
The default setting is 12 hours.
Add data recovery rights to a user
- Go to your WALLIX ONE IDaaS admin page
- Go to Users and select an existing user
- Click Edit then Add an attribute
- Provide the following attribute:
name: recovery_data
kind: bool
value: true
When this user will log in the Enterprise Vault user app, and if he is the first one with recovery rights (data or account), he will have the following message:
In fact, specific encryption keys are required to carry out recovery operations.
These are created when the first admin is authenticated.
Consequently, for subsequent admins, an admin who has the keys must share them.
- Go to your Enterprise Vault user app with an admin who has the recovery key
- Go to Settings, then Recovery keys
- Click Activate access for the new admins
Add quorum rights to a user
- Go to your WALLIX ONE IDaaS admin page
- Go to Users and select an existing user
- Click Edit then Add an attribute
- Provide the following attribute:
name: recovery_data_workflow
kind: bool
value: true
Define the quorum
- Go to your Enterprise Vault user app with an admin who has the quorum rights
- Go to Settings, then Approvers groups
- Click Add group
- Choose a name and a quorum number (number of validation needed to accept the request), then click Save
- Click + on the Users column, then provide the approvers email address then click Validate
Press "Enter" if you want to add multiple approvers
- Click the Group name the Quorum or the Users if you need to change an information
- Click Save
Workflow
The admin requests the access to a specific user account
- The admin goes to his Enterprise Vault user app
- He clicks on Recovery then Data recovery
- He selects a user, then click Send
- The request appears in the history
The quorum members are notified and accept the request
- A quorum user goes to his Enterprise Vault user app
- He clicks Recovery then Approbation requests
- He clicks Approve or Dismiss
The admin has access to the user personal items
- The admin logout from his web client then perform a new authentication
- He clicks his profile
- He selects the user account
- He has access to the user's personal items
As mentioned in the introduction, it is only possible to retrieve secrets from the personal vault.
Any other action will display an error, which indicates that it is prohibited.
Synchronizing Trustelem Groups with the Enterprise Vault CLI (BETA)
🎯 Goal
Automatically define access rights to shared vaults and collections in Enterprise Vault based on membership in Trustelem groups, using a custom JSON attribute called vaultSync
.
🧩 Overall Workflow
The script reads all Trustelem groups that include the vaultSync
attribute.
-
For each group:
-
A shared vault is created or updated.
-
Collections are created or removed according to the configuration.
-
User permissions are applied.
-
-
If a user also has a
vaultSync
attribute, it overrides the group configuration.
🧷 Trustelem Configuration
Step 1 – Add custom attributes
🔹 vaultSync
JSON attribute on a Trustelem Group (mandatory)
Example to adapt:
{
"sharedVault": "SharedVault1",
"collections": ["Collec1", "Collec2"],
"createCollections": true,
"deleteCollections": false,
"role": "User",
"permission": "view"
}
Field | Type | Description |
---|---|---|
sharedVault |
string |
Name of the shared vault to sync |
collections |
string[] |
List of collections to manage |
createCollections |
boolean |
Auto-create missing collections |
deleteCollections |
boolean |
Auto-remove collections not listed |
role |
string |
User role in the vault: "Owner" , "Admin" , or "User" |
permission |
string |
Permission in the collection: "view" , "viewExceptPass" , "edit" , "editExceptPass" , "manage" |
🔹 vaultSync
JSON attribute on a Trustelem User (optional)
Overrides group settings when applied.
Example to adapt:
[
{
"sharedVault": "SharedVault1",
"collections": ["Collec1"],
"role": "Admin",
"permission": "edit"
}
]
Step 2 – Generate a Trustelem API Key
-
In the Trustelem admin console, go to Rest API > New API key
⚠️if you can't see the Rest API tab, you have to create a ticket to require the feature. -
Click the edit (pencil) icon
-
Check:
-
users_read
-
groups_read
-
-
Save.
-
Note the following values:
-
KEY ID
-
Bearer Token
-
🛠 CLI Script Configuration
1/ Download Enterprise Vault CLI.
2/ Create the synchro
script
Example with the Linux CLI:
#!/bin/bash
# --- Configuration ---
vault_id="to_replace"
vault_secret="to_replace"
vault_password="to_replace"
vault_url="to_replace"
trustelem_key_id="to_replace"
trustelem_bearer="to_replace"
trustelem_url="to_replace"
# --- Function: Connect and unlock the Vault CLI ---
connect_to_vault() {
./wv logout > /dev/null 2>&1
./wv config server "$vault_url" > /dev/null 2>&1
export WV_CLIENTID=$vault_id
export WV_CLIENTSECRET=$vault_secret
export WV_TRUSTELEMKEYID=$trustelem_key_id
export WV_TRUSTELEMBEARER=$trustelem_bearer
export WV_TRUSTELEMURL=$trustelem_url
./wv login --apikey > /dev/null 2>&1
export WV_SESSION=$(./wv unlock "$vault_password" --raw)
}
# --- Main Execution ---
connect_to_vault
./wv syncgroups
PowerShell example with the Windows CLI:
# --- Configuration ---
$vault_id = "to_replace"
$vault_secret = "to_replace"
$vault_password = "to_replace"
$vault_url = "to_replace"
$trustelem_key_id = "to_replace"
$trustelem_bearer = "to_replace"
$trustelem_url = "to_replace"
# --- Function: Connect and unlock the Vault CLI ---
function Connect-ToVault {
./wv.exe logout | Out-Null
./wv.exe config server $vault_url | Out-Null
$env:WV_CLIENTID = $vault_id
$env:WV_CLIENTSECRET = $vault_secret
$env:WV_TRUSTELEMKEYID = $trustelem_key_id
$env:WV_TRUSTELEMBEARER = $trustelem_bearer
$env:WV_TRUSTELEMURL = $trustelem_url
./wv.exe login --apikey | Out-Null
$session = ./wv.exe unlock $vault_password --raw
$env:WV_SESSION = $session.Trim()
}
# --- Main Execution ---
Connect-ToVault
./wv.exe syncgroups
Values to replace:
Variable | Description |
---|---|
vault_id |
API service account ID (web client > Account parameters > Security > API Keys) |
vault_secret |
API service account secret (web client > Account parameters > Security > API Keys) |
vault_password |
Master password for the service account |
vault_url |
Vault instance URL (e.g., https://vault-yourdomain.trustelem.com ) |
trustelem_key_id |
KEY ID from Step 2 |
trustelem_bearer |
Bearer Token from Step 2 |
trustelem_url |
Trustelem admin URL (e.g., https://admin-yourdomain.trustelem.com ) |
3/ Start the script.
⚙️ Detailed Synchronization Behavior
1. Shared Vault Management
⚠️ Important: if the service account is not a shared vault member, it has no way to know if the shared vault already exists or not. In this case, the script will assume the shared vault doesn't exist and a new shared vault with the same name will be created.
2. Collection Management
-
With
createCollections=true
:-
Collections missing in the vault but listed in the JSON will be created.
-
The service account is given
manage
rights on these.
-
-
With
deleteCollections=true
:-
Collections present in the vault but not in the list will be deleted.
-
The service account must have
manage
rights to delete them.
-
-
If
collections = ["*"]
:-
No automatic create or delete, regardless of
createCollections
ordeleteCollections
.
-
⚠️ Important: do not set both createCollections=true
and deleteCollections=true
at the same time.
🔸 Note on User Attributes: User-level vaultSync
attributes cannot create or delete collections—only assign permissions.
3. User Membership & Permissions
-
If a user is not in Vault:
-
An error is returned.
-
-
Adding users to collections:
-
If the user is not already in a listed collection (or
"*"
), they are added with therole
andpermission
defined. -
If the user has their own
vaultSync
config, it overrides the group config. -
The service account must have
"manage"
rights.
-
-
Updating permissions:
-
If the user has different permissions in a collection, they are updated accordingly.
-
Requires
"manage"
permission.
-
-
Removing from collections:
-
If a user is in a collection not listed, they are removed.
-
Requires
"manage"
permission.
-
🧾 Special Cases
Scenario | Behavior |
---|---|
🔁 Trustelem group renamed in AD | Synchronization continues (attribute remains present) |
🗑 Trustelem group deleted | Synchronization stops, but the vault remains unchanged |
♻️ Group deleted and recreated | Vault is no longer linked; re-adding the attribute resumes sync |
✅ Permissions Summary
Action | Required Right (Service Account) |
---|---|
Create shared vault | None (becomes Owner ) |
Modify existing vault | Must be Owner |
Create/delete collection | manage |
Add/remove users from collections | manage |
Update user permissions | manage |