IBeam.Management.Secrets.AzureKeyVault
2.16.0
dotnet add package IBeam.Management.Secrets.AzureKeyVault --version 2.16.0
NuGet\Install-Package IBeam.Management.Secrets.AzureKeyVault -Version 2.16.0
<PackageReference Include="IBeam.Management.Secrets.AzureKeyVault" Version="2.16.0" />
<PackageVersion Include="IBeam.Management.Secrets.AzureKeyVault" Version="2.16.0" />
<PackageReference Include="IBeam.Management.Secrets.AzureKeyVault" />
paket add IBeam.Management.Secrets.AzureKeyVault --version 2.16.0
#r "nuget: IBeam.Management.Secrets.AzureKeyVault, 2.16.0"
#:package IBeam.Management.Secrets.AzureKeyVault@2.16.0
#addin nuget:?package=IBeam.Management.Secrets.AzureKeyVault&version=2.16.0
#tool nuget:?package=IBeam.Management.Secrets.AzureKeyVault&version=2.16.0
IBeam.Management.Secrets.AzureKeyVault
Optional writable IManagementSecretStore for portal connection keys. Register AddIBeamManagementKeyVaultSecrets with a dedicated SecretClient constructed by the host. Grant that managed identity secret get/set access only to the management vault. Never enable SDK HTTP content logging or log portal request bodies/management key headers.
Each submission creates a unique application/organization-scoped secret with a versioned reference. References cannot choose a vault, another application or an unversioned latest value. Rows contain only references; secret values are excluded from serialization and ToString. Provider errors are translated without SDK messages, response bodies or inner exceptions.
No vault creation, deployment, deletion, purge or secret enumeration is performed. Failed validation or a lost concurrent activation can leave an unreferenced secret/version or verified metadata row; retain and clean those through separately authorized operational tooling. Never remove a secret still referenced by an active connection.
Client setup and managed identity guidance: https://learn.microsoft.com/en-us/dotnet/api/overview/azure/security.keyvault.secrets-readme
Deployment configuration, identity storage choices, MFA/bootstrap, onboarding, exact registrations/endpoints, network/proxy policy, secret rotation, audit retention/failure behavior and the deferred consumer host are covered by the Management deployment handoff. Source/history isolation describes which historical rows may be exposed. Generated-package validation uses the package-only two-target smoke sample; IBM-0097 supplies independent host-owned errors/logs sanitization switches, safe by default and restricted to explicit non-Production contexts. See sanitization settings.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Azure.Security.KeyVault.Secrets (>= 4.11.2)
- IBeam.Management (>= 2.16.0)
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 10.0.3)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 2.16.0 | 34 | 10/20/2026 |
| 2.15.0 | 60 | 10/17/2026 |
| 2.15.0-rc.1 | 57 | 10/17/2026 |