We are using the new PowerShell Secrets Manager to bring in our password manager (Keeper) records with Dynamic Credentials.
They work great for connections. However, we would also like to be able to reference them in other Dynamic Credential scripts. Currently using them in a cascading manor like that doesn't work. In other words, the EffectiveUsername and EffectivePassword values are empty if the referenced credential is a Dynamic Credential.
We have worked around it by having the other Dynamic Folder fetch records from secrets manager directly, but that now means there is duplicate code.
Allowing Dynamic Credential lookups to cascade would allow for better code management so we can keep all the secrets manager lookups in one place. I think it could also make Dynamic Credentials more useful in other scenarios also.
Ramon Medina
We are using the new PowerShell Secrets Manager to bring in our password manager (Keeper) records with Dynamic Credentials.
They work great for connections. However, we would also like to be able to reference them in other Dynamic Credential scripts. Currently using them in a cascading manor like that doesn't work. In other words, the EffectiveUsername and EffectivePassword values are empty if the referenced credential is a Dynamic Credential.
We have worked around it by having the other Dynamic Folder fetch records from secrets manager directly, but that now means there is duplicate code.
Allowing Dynamic Credential lookups to cascade would allow for better code management so we can keep all the secrets manager lookups in one place. I think it could also make Dynamic Credentials more useful in other scenarios also.