Microsoft.Azure.KeyVault.WebKey 3.0.5
Microsoft Azure Key Vault WebKey Class Library
This library has been replaced by the following new Azure SDKs. You can read about the new Azure SDKs at https://aka.ms/azsdkvalueprop.
The latest libraries to interact with the Azure KeyVault service are:
* https://www.nuget.org/packages/Azure.Security.KeyVault.Keys
* https://www.nuget.org/packages/Azure.Security.KeyVault.Secrets
* https://www.nuget.org/packages/Azure.Security.KeyVault.Certificates
It is recommended that you move to the new package.
Showing the top 20 packages that depend on Microsoft.Azure.KeyVault.WebKey.
| Packages | Downloads |
|---|---|
|
Microsoft.Azure.KeyVault
Azure Key Vault enables users to store and use cryptographic keys within the Microsoft Azure environment. Azure Key Vault supports multiple key types and algorithms and enables the use of Hardware Security Modules (HSM) for high value customer keys. In addition, Azure Key Vault allows users to securely store secrets in a Key Vault; secrets are limited size octet objects and Azure Key Vault applies no specific semantics to these objects. A Key Vault may contain a mix of keys and secrets at the same time, and access control for the two types of object is independently controlled. Users, subject to appropriate authorization, may: 1) Manage cryptographic keys using Create, Import, Update, Delete and other operations 2) Manage secrets using Get, Set, Delete and other operations 3) Use cryptographic keys with Sign/Verify, WrapKey/UnwrapKey and Encrypt/Decrypt operations. Operations against Key Vaults are authenticated and authorized using Azure Active Directory.
|
9 |
|
Microsoft.Azure.KeyVault
Azure Key Vault enables users to store and use cryptographic keys within the Microsoft Azure environment. Azure Key Vault supports multiple key types and algorithms and enables the use of Hardware Security Modules (HSM) for high value customer keys. In addition, Azure Key Vault allows users to securely store secrets in a Key Vault; secrets are limited size octet objects and Azure Key Vault applies no specific semantics to these objects. A Key Vault may contain a mix of keys and secrets at the same time, and access control for the two types of object is independently controlled. Users, subject to appropriate authorization, may: 1) Manage cryptographic keys using Create, Import, Update, Delete and other operations 2) Manage secrets using Get, Set, Delete and other operations 3) Use cryptographic keys with Sign/Verify, WrapKey/UnwrapKey and Encrypt/Decrypt operations. Operations against Key Vaults are authenticated and authorized using Azure Active Directory.
|
8 |
|
Microsoft.Azure.KeyVault
Azure Key Vault enables users to store and use cryptographic keys within the Microsoft Azure environment. Azure Key Vault supports multiple key types and algorithms and enables the use of Hardware Security Modules (HSM) for high value customer keys. In addition, Azure Key Vault allows users to securely store secrets in a Key Vault; secrets are limited size octet objects and Azure Key Vault applies no specific semantics to these objects. A Key Vault may contain a mix of keys and secrets at the same time, and access control for the two types of object is independently controlled. Users, subject to appropriate authorization, may: 1) Manage cryptographic keys using Create, Import, Update, Delete and other operations 2) Manage secrets using Get, Set, Delete and other operations 3) Use cryptographic keys with Sign/Verify, WrapKey/UnwrapKey and Encrypt/Decrypt operations. Operations against Key Vaults are authenticated and authorized using Azure Active Directory. Key Vault now supports certificates, a complex type that makes use of existing key and secret infrastructure for certificate operations. KV certificates also support notification and auto-renewal as well as other management features.
|
6 |
|
Microsoft.Azure.KeyVault
Azure Key Vault enables users to store and use cryptographic keys within the Microsoft Azure environment. Azure Key Vault supports multiple key types and algorithms and enables the use of Hardware Security Modules (HSM) for high value customer keys. In addition, Azure Key Vault allows users to securely store secrets in a Key Vault; secrets are limited size octet objects and Azure Key Vault applies no specific semantics to these objects. A Key Vault may contain a mix of keys and secrets at the same time, and access control for the two types of object is independently controlled. Users, subject to appropriate authorization, may: 1) Manage cryptographic keys using Create, Import, Update, Delete and other operations 2) Manage secrets using Get, Set, Delete and other operations 3) Use cryptographic keys with Sign/Verify, WrapKey/UnwrapKey and Encrypt/Decrypt operations. Operations against Key Vaults are authenticated and authorized using Azure Active Directory.
|
6 |
|
Microsoft.Azure.KeyVault
Azure Key Vault enables users to store and use cryptographic keys within the Microsoft Azure environment. Azure Key Vault supports multiple key types and algorithms and enables the use of Hardware Security Modules (HSM) for high value customer keys. In addition, Azure Key Vault allows users to securely store secrets in a Key Vault; secrets are limited size octet objects and Azure Key Vault applies no specific semantics to these objects. A Key Vault may contain a mix of keys and secrets at the same time, and access control for the two types of object is independently controlled. Users, subject to appropriate authorization, may: 1) Manage cryptographic keys using Create, Import, Update, Delete and other operations 2) Manage secrets using Get, Set, Delete and other operations 3) Use cryptographic keys with Sign/Verify, WrapKey/UnwrapKey and Encrypt/Decrypt operations. Operations against Key Vaults are authenticated and authorized using Azure Active Directory. Key Vault now supports certificates, a complex type that makes use of existing key and secret infrastructure for certificate operations. KV certificates also support notification and auto-renewal as well as other management features.
This library has been replaced by the following new Azure SDKs. You can read about the new Azure SDKs at https://aka.ms/azsdkvalueprop.
The latest libraries to interact with the Azure KeyVault service are:
* https://www.nuget.org/packages/Azure.Security.KeyVault.Keys
* https://www.nuget.org/packages/Azure.Security.KeyVault.Secrets
* https://www.nuget.org/packages/Azure.Security.KeyVault.Certificates
It is recommended that you move to the new package.
|
6 |
|
Microsoft.Azure.KeyVault
Azure Key Vault enables users to store and use cryptographic keys within the Microsoft Azure environment. Azure Key Vault supports multiple key types and algorithms and enables the use of Hardware Security Modules (HSM) for high value customer keys. In addition, Azure Key Vault allows users to securely store secrets in a Key Vault; secrets are limited size octet objects and Azure Key Vault applies no specific semantics to these objects. A Key Vault may contain a mix of keys and secrets at the same time, and access control for the two types of object is independently controlled. Users, subject to appropriate authorization, may: 1) Manage cryptographic keys using Create, Import, Update, Delete and other operations 2) Manage secrets using Get, Set, Delete and other operations 3) Use cryptographic keys with Sign/Verify, WrapKey/UnwrapKey and Encrypt/Decrypt operations. Operations against Key Vaults are authenticated and authorized using Azure Active Directory. Key Vault now supports certificates, a complex type that makes use of existing key and secret infrastructure for certificate operations. KV certificates also support notification and auto-renewal as well as other management features.
|
5 |
|
Microsoft.Azure.KeyVault
Azure Key Vault enables users to store and use cryptographic keys within the Microsoft Azure environment. Azure Key Vault supports multiple key types and algorithms and enables the use of Hardware Security Modules (HSM) for high value customer keys. In addition, Azure Key Vault allows users to securely store secrets in a Key Vault; secrets are limited size octet objects and Azure Key Vault applies no specific semantics to these objects. A Key Vault may contain a mix of keys and secrets at the same time, and access control for the two types of object is independently controlled. Users, subject to appropriate authorization, may: 1) Manage cryptographic keys using Create, Import, Update, Delete and other operations 2) Manage secrets using Get, Set, Delete and other operations 3) Use cryptographic keys with Sign/Verify, WrapKey/UnwrapKey and Encrypt/Decrypt operations. Operations against Key Vaults are authenticated and authorized using Azure Active Directory. Key Vault now supports certificates, a complex type that makes use of existing key and secret infrastructure for certificate operations. KV certificates also support notification and auto-renewal as well as other management features.
|
4 |
|
Microsoft.Azure.KeyVault
Azure Key Vault enables users to store and use cryptographic keys within the Microsoft Azure environment. Azure Key Vault supports multiple key types and algorithms and enables the use of Hardware Security Modules (HSM) for high value customer keys. In addition, Azure Key Vault allows users to securely store secrets in a Key Vault; secrets are limited size octet objects and Azure Key Vault applies no specific semantics to these objects. A Key Vault may contain a mix of keys and secrets at the same time, and access control for the two types of object is independently controlled. Users, subject to appropriate authorization, may: 1) Manage cryptographic keys using Create, Import, Update, Delete and other operations 2) Manage secrets using Get, Set, Delete and other operations 3) Use cryptographic keys with Sign/Verify, WrapKey/UnwrapKey and Encrypt/Decrypt operations. Operations against Key Vaults are authenticated and authorized using Azure Active Directory. Key Vault now supports certificates, a complex type that makes use of existing key and secret infrastructure for certificate operations. KV certificates also support notification and auto-renewal as well as other management features.
|
3 |
|
Microsoft.Azure.KeyVault
Azure Key Vault enables users to store and use cryptographic keys within the Microsoft Azure environment. Azure Key Vault supports multiple key types and algorithms and enables the use of Hardware Security Modules (HSM) for high value customer keys. In addition, Azure Key Vault allows users to securely store secrets in a Key Vault; secrets are limited size octet objects and Azure Key Vault applies no specific semantics to these objects. A Key Vault may contain a mix of keys and secrets at the same time, and access control for the two types of object is independently controlled. Users, subject to appropriate authorization, may: 1) Manage cryptographic keys using Create, Import, Update, Delete and other operations 2) Manage secrets using Get, Set, Delete and other operations 3) Use cryptographic keys with Sign/Verify, WrapKey/UnwrapKey and Encrypt/Decrypt operations. Operations against Key Vaults are authenticated and authorized using Azure Active Directory. Key Vault now supports certificates, a complex type that makes use of existing key and secret infrastructure for certificate operations. KV certificates also support notification and auto-renewal as well as other management features.
|
2 |
|
Microsoft.Azure.KeyVault
Azure Key Vault enables users to store and use cryptographic keys within the Microsoft Azure environment. Azure Key Vault supports multiple key types and algorithms and enables the use of Hardware Security Modules (HSM) for high value customer keys. In addition, Azure Key Vault allows users to securely store secrets in a Key Vault; secrets are limited size octet objects and Azure Key Vault applies no specific semantics to these objects. A Key Vault may contain a mix of keys and secrets at the same time, and access control for the two types of object is independently controlled. Users, subject to appropriate authorization, may: 1) Manage cryptographic keys using Create, Import, Update, Delete and other operations 2) Manage secrets using Get, Set, Delete and other operations 3) Use cryptographic keys with Sign/Verify, WrapKey/UnwrapKey and Encrypt/Decrypt operations. Operations against Key Vaults are authenticated and authorized using Azure Active Directory. Key Vault now supports certificates, a complex type that makes use of existing key and secret infrastructure for certificate operations. KV certificates also support notification and auto-renewal as well as other management features.
|
1 |
Added recommendation to use new libraries listed in the package description.
.NET Framework 4.5.2
- Microsoft.Rest.ClientRuntime (>= 2.3.20 && < 3.0.0)
- Microsoft.Rest.ClientRuntime.Azure (>= 3.3.18 && < 4.0.0)
- Newtonsoft.Json (>= 10.0.3)
.NET Standard 2.0
- System.Security.Cryptography.Cng (>= 4.3.0)
- System.Security.Cryptography.Algorithms (>= 4.3.0)
- System.Runtime (>= 4.3.0)
- System.Net.Http (>= 4.3.4)
- System.Linq (>= 4.3.0)
- System.Collections.Concurrent (>= 4.3.0)
- System.Collections (>= 4.3.0)
- Newtonsoft.Json (>= 10.0.3)
- Microsoft.Rest.ClientRuntime.Azure (>= 3.3.18 && < 4.0.0)
- Microsoft.Rest.ClientRuntime (>= 2.3.20 && < 3.0.0)
.NET Standard 1.4
- System.Security.Cryptography.Cng (>= 4.3.0)
- System.Runtime (>= 4.3.0)
- System.Security.Cryptography.Algorithms (>= 4.3.0)
- System.Linq (>= 4.3.0)
- System.Net.Http (>= 4.3.4)
- Microsoft.Rest.ClientRuntime (>= 2.3.20 && < 3.0.0)
- NETStandard.Library (>= 1.6.1)
- Newtonsoft.Json (>= 10.0.3)
- System.Collections (>= 4.3.0)
- System.Collections.Concurrent (>= 4.3.0)
- Microsoft.Rest.ClientRuntime.Azure (>= 3.3.18 && < 4.0.0)
.NET Framework 4.6.1
- Microsoft.Rest.ClientRuntime (>= 2.3.20 && < 3.0.0)
- Microsoft.Rest.ClientRuntime.Azure (>= 3.3.18 && < 4.0.0)
- Newtonsoft.Json (>= 10.0.3)
| Version | Downloads | Last updated |
|---|---|---|
| 3.0.5 | 7 | 08/25/2023 |
| 3.0.4 | 7 | 08/26/2023 |
| 3.0.3 | 6 | 08/25/2023 |
| 3.0.2 | 5 | 02/15/2024 |
| 3.0.1 | 7 | 08/28/2023 |
| 3.0.0 | 7 | 08/31/2023 |
| 3.0.0-alpha | 6 | 06/12/2023 |
| 2.1.0-preview | 7 | 06/11/2023 |
| 2.0.7 | 7 | 08/29/2023 |
| 2.0.6 | 7 | 08/28/2023 |
| 2.0.5 | 6 | 08/27/2023 |
| 2.0.4 | 4 | 08/26/2023 |
| 2.0.3-preview | 8 | 06/13/2023 |
| 2.0.2-preview | 7 | 06/12/2023 |
| 2.0.0-preview | 7 | 06/12/2023 |