This repository was archived by the owner on Jun 22, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 22, 2026. It is now read-only.
Request: Multiple instances of SecretStore #58
Description
I don't know if this is a documentation issue or a bug, so I'll ask. I have a vault registered using Microsoft.PowerShell.SecretStore. I then tried to create a second vault.
Register-SecretVault -Name demo -Description "test vault" -ModuleName microsoft.powershell.secretstoreGet-SecretVault shows it. I have nothing in the vault but if I run Get-SecretInfo, I see all the entries from my default vault, even though the vault name shows the new demo vault. Are we limited to one vault per user of a given module? If so, that needs to be clearer in the documentation.
Activity
jdhitsolutions commentedon Apr 16, 2021
Clearly, there is some sort of interaction happening.
PaulHigin commentedon Apr 21, 2021
SecretManagement allows an extension vault to be registered multiple times, because it is possible that an extension vault may support different contexts via the registration
VaultParameters. However, theSecretStorevault currently always operates in the logged on user scope (see SecretStore documentation: https://github.com/powershell/secretstore).So registering
SecretStoremultiple times with different names just results in duplication of the same store, and doesn't make sense.But we decided to allow this for maximum flexibility.
jdhitsolutions commentedon Apr 21, 2021
Ok then. Again, it would help to have this clearer in the documentation. The bottom line is that a user can only have 1 microsoft.powershell.secretstore vault per user scope. That's too bad because I can imagine a situation where I might want 2 stores based on the default Microsoft.PowerShell.SecretStore. Or are you expecting that people will really be using an extension vault like LastPass?
SydneyhSmith commentedon Apr 26, 2021
Thanks Jeff Hicks (@jdhitsolutions) I'd love to better understand why a user may want multiple SecretStore instances in a particular user scope, does having secretmetadata help users to organize their secrets in a way that doesnt require a second instance of the store?
Agree that we can make this more clear in the SecretStore documentation
jdhitsolutions commentedon Apr 26, 2021
I might want one store with data that is associated with a module or CI/CD project I'm running and a second store for personal items. I might want one group of data to have a longer unlock time and another set to be more secure. A single store means every secret is treated the same and maybe that isn't what I want.
[-]Are multiple vaults allowed?[/-][+]Request: Multiple instances of SecretStore[/+]PetriAsi commentedon Jul 31, 2021
I have same king of needs with Jeff Hicks (@jdhitsolutions) . Also custom or third party modules will benefit if secretstore can be register multiple times with different names and instances. Then custom module can create it's own store for it's secrets.
SjoerdV commentedon Oct 31, 2021
Really need this as well. The use case is:
craibuc commentedon Nov 28, 2022
I'd like to have multiple
Microsoft.PowerShell.SecretStoreSecretStores to segment secrets between clients.PaulHigin commentedon Nov 28, 2022
Sounds like there is a need for multiple store instances. Adding PS-Committee review for visibility.
/cc: Steve Lee (@SteveL-MSFT), Sydney Smith (@SydneyhSmith)
craibuc commentedon Nov 29, 2022
Is there a way to create independent,
Microsoft.PowerShell.SecretStoreinstances by supplying values to-VaultParameters?ckolumbus commentedon Apr 4, 2024
Paul Higinbotham (@PaulHigin) this topic seems to be stale for a while again, but I need exactly the same functionality. So a +1 for this topic from my side.
Pseudolegend commentedon Jun 18, 2024
I would also find this feature useful.
lastphoenx commentedon Jul 12, 2024
I would also find this feature extremly useful. I totally agree with the uses-cases mentionned before.
ArieHein commentedon Sep 7, 2024
I wanted to create two vaults based on SecretStore, per environment :
register-SecretVault -name SecretStoreDev -ModuleName Microsoft.PowerShell.SecretStore -Description "Dev Vault"register-SecretVault -name SecretStoreProd -ModuleName Microsoft.PowerShell.SecretStore -Description "Prod Vault"But its not enough to be able to have them, they need to be separated when you use
Get-SecretStoreConfigurationand when you use
Set-SecretStoreConfigurationas i would like differernt passwords for each and locking behavior as example.