rai

Hi

is it possible to add the button for copying both username and password at the same time, for PAM vault accounts, similar to the username and password entries in personal vaults?

Hi, i also think this feature could be beneficial and provide a much better experience for users, when only one possible elevation is available.

Hi

I would like to request a feature, to control what type of entries are allowed in a certain shared vault.

Use case: Making a shared credentials vault for different teams, in which only credential related (username/password) entries are allowed.

Thanks

Thanks for the response! I was initially told, by the support, that this was not the case, and it was suggested that i make this feature request, hence why we are here. Happy to hear that it is indeed possible.

I will give it a look, when i get to it. Otherwise, i will reach out for assistance.

Thanks!

Hi

I would like to suggest an idea related to providers in PAM. In a cloned multi-environment, meaning each environment (PROD, UAT, DEV) is a clone of the production environment, Domain controllers are also replicated with the same name, etc. The environments are seperated on a network level. This causes an issue, when wanting to manage accounts in the different environments, as it is not currently possible to refer to domain controllers other than by name.

"DomainController_A" in PROD can only be added once as a PAM provider (assuming DVLS server is running in PROD), while "DomainControlller_A" in DEV can not be added. Thereby, the accounts in DEV can not be managed by the PAM module.

It would be beneficial if support for such environments can be implemented.

Maybe the "easy" way of doing it, is allowing to reference the domain controllers by IP addresses, which would be different in each environment. Meaning that you are able to reference the domain controllers by a set of IP addresses (additionally being able to asign a display name per IP address in the DVLS interface, for each DC), so that the PAM module is not dependent on one DC, but rather the full set of DCs for availability purposes.

Another possible solutions could be having an "agent" in each environment, talking back to the DVLS server, allowing DVLS Server and the agents to handle identity of DCs, password and account management etc. with custom IDs for each DC, completely not relying on the actual environment setup. Maybe a more bullet proof solution and also more compatible with different customer environments.

Thanks!