Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle multiple CyberArk Vaults #1

Open
aaearon opened this issue Mar 15, 2021 · 1 comment
Open

Handle multiple CyberArk Vaults #1

aaearon opened this issue Mar 15, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@aaearon
Copy link
Owner

aaearon commented Mar 15, 2021

Right now we depend on the user to manage PASSession on their own. This makes it next to impossible to have users add multiple SecretManagement.CyberArk SecretVaults (use case: Multiple CyberArk environments, etc.)

We should handle the PASSession on behalf of the user and as long as they pass the needed parameters as part of VaultParameters when using Register-SecretVault.

Example of how this could look

$Parameters = @{ 
    BaseURI="https://cyberark-production.example.com"
    type="CyberArk"
    Credential="$Credentials"
    concurrentSession=$true 
}

Register-SecretVault -Name ProductionVault -ModuleName SecretManagement.CyberArk -VaultParameters $Parameters -DefaultVault
@aaearon aaearon added the enhancement New feature or request label Mar 15, 2021
@NathanielMaier
Copy link

Great idea! As I mentioned over in pspete/psPAS#317, it'd also be nice to allow the Credential retrieved through the CCP or CP, via the CredentialRetriever module.

aaearon pushed a commit that referenced this issue Aug 20, 2022
Copy SecretManagement module from old repo to new
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants