Question
What are minimum authorizations a user is required to have in order to create the Vault environment for an application?
Answer
There are two levels of authorizations that the user installing the provider requires to have:
- Vault level authorization:
- Add Safes - This is required only if a new Provider configuration Safe is to be created. If the provider is going to be sharing the configuration files from an already existing Safe (possible with providers of the same platform only) see the Safe authorization level section
- Manage users - This is in order to create the provider and / or Application user
- Audit Users
- Safe level authorizations:
When more than one Provider is installed and configured to work with the same configuration Safe, for the second and subsequent installations, the user installing the Provider requires the following authorizations:
- On the existing Provider configuration Safe (by default called AppProviderConf):
- Use passwords
- Retrieve passwords
- List passwords
- Add passwords
- Update password value
- Update passwords properties
- Rename passwords
- Create folders
- On the Safes where the passwords that it needs to be able to access are stored:
- Use passwords
- List passwords
- Retrieve passwords
- View audit
- View Safe Members
Notes:
- If the Safe is configured to require confirmation from authorized users before passwords can be retrieved, the Provider user and the application user should have the following authorization:
- Access Safe without Confirmation
- To be able to grant all of these authorizations, the user used to install the provider need to have these authorizations himself.
Issue
Q:
What are minimum authorizations a user is required to have in order to create the Vault environment for an application
A:
There are two levels of authorizations that the user installing the provider requires to have:
- Vault level authorization:
- Add Safes - This is required only if a new Provider configuration Safe is to be created. If the provider is going to be sharing the configuration files from an already existing Safe (possible with providers of the same platform only) see the Safe authorization level section
- Manage users - This is in order to create the provider and / or Application user
- Audit Users
- Safe level authorizations:
When more than one Provider is installed and configured to work with the same configuration Safe, for the second and subsequent installations, the user installing the Provider requires the following authorizations:
- On the existing Provider configuration Safe (by default called AppProviderConf):
- Use passwords
- Retrieve passwords
- List passwords
- Add passwords
- Update password value
- Update passwords properties
- Rename passwords
- Create folders
- On the Safes where the passwords that it needs to be able to access are stored:
- Use passwords
- List passwords
- Retrieve passwords
- View audit
- View Safe Members
Notes:
- If the Safe is configured to require confirmation from authorized users before passwords can be retrieved, the Provider user and the application user should have the following authorization:
- Access Safe without Confirmation
- To be able to grant all of these authorizations, the user used to install the provider need to have these authorizations himself.
Q:
What are minimum authorizations a user is required to have in order to create the Vault environment for an application
A:
There are two levels of authorizations that the user installing the provider requires to have:
- Vault level authorization:
- Add Safes - This is required only if a new Provider configuration Safe is to be created. If the provider is going to be sharing the configuration files from an already existing Safe (possible with providers of the same platform only) see the Safe authorization level section
- Manage users - This is in order to create the provider and / or Application user
- Audit Users
- Safe level authorizations:
When more than one Provider is installed and configured to work with the same configuration Safe, for the second and subsequent installations, the user installing the Provider requires the following authorizations:
- On the existing Provider configuration Safe (by default called AppProviderConf):
- Use passwords
- Retrieve passwords
- List passwords
- Add passwords
- Update password value
- Update passwords properties
- Rename passwords
- Create folders
- On the Safes where the passwords that it needs to be able to access are stored:
- Use passwords
- List passwords
- Retrieve passwords
- View audit
- View Safe Members
Notes:
- If the Safe is configured to require confirmation from authorized users before passwords can be retrieved, the Provider user and the application user should have the following authorization:
- Access Safe without Confirmation
- To be able to grant all of these authorizations, the user used to install the provider need to have these authorizations himself.