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
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.CyberArkSecretVaults (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
VaultParameterswhen usingRegister-SecretVault.Example of how this could look