Register-SecretVault allows registering same extension vault more than once about secretmanagement

[issue-label-bot]

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.85. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[adityapatwardhan]

In addition to that it allows the -DefaultVault to be used even if an vault is registered as default.

[PaulHigin]

@SteveL-MSFT Please provide repro steps. We already check vault name and allow only one registered, so I assume you mean we should disallow registering the same extension vault under different names?

[daxian-dbw]

I assume you mean we should disallow registering the same extension vault under different names?

I think it could be useful to allow registering the same extension vault under different names, so a user's secrets can be categorized.

[SteveL-MSFT]

@PaulHigin yes, same vault extension under different names. In my case, I had just installed a newer version of SecretStore and re-registered it. When enumerating the vaults, I saw I had registered SecretStore twice under different names and one was default and the other wasn't. Since the secrets are stored in the same vault, I don't think there's a use case to support this.

[daxian-dbw]

Since the secrets are stored in the same vault, I don't think there's a use case to support this.

If the secrets are stored in the same place for both registered vault, then I agree that we should disallow registering the same extension more than once.

[SydneyhSmith]

Also related: https://github.com/PowerShell/SecretStore/issues/35

[SteveL-MSFT]

A use case we discussed is for extension vaults that support partitions or namespaces. In this case, it would make sense to allow multiple registrations where each one is registered to a specific namespace within that vault.

[SydneyhSmith]

Closing as by design-- a user may want to use the say extension vault multiple times with different configurations