diff --git a/eng/jacoco-test-coverage/pom.xml b/eng/jacoco-test-coverage/pom.xml index 9ff09c510ead1..20a46b3eafa45 100644 --- a/eng/jacoco-test-coverage/pom.xml +++ b/eng/jacoco-test-coverage/pom.xml @@ -273,7 +273,7 @@ com.azure azure-security-keyvault-jca - 2.7.0-beta.1 + 2.8.0-beta.1 com.azure diff --git a/eng/versioning/version_client.txt b/eng/versioning/version_client.txt index dc57248dbe845..5679510833e18 100644 --- a/eng/versioning/version_client.txt +++ b/eng/versioning/version_client.txt @@ -123,7 +123,7 @@ com.azure:azure-security-attestation;1.1.2;1.2.0-beta.1 com.azure:azure-security-confidentialledger;1.0.0-beta.2;1.0.0-beta.3 com.azure:azure-security-keyvault-administration;4.1.2;4.2.0-beta.1 com.azure:azure-security-keyvault-certificates;4.3.2;4.4.0-beta.1 -com.azure:azure-security-keyvault-jca;2.6.0;2.7.0-beta.1 +com.azure:azure-security-keyvault-jca;2.7.0;2.8.0-beta.1 com.azure:azure-security-test-keyvault-jca;1.0.0;1.0.0 com.azure:azure-security-keyvault-keys;4.4.2;4.5.0-beta.1 com.azure:azure-security-keyvault-secrets;4.4.2;4.5.0-beta.1 diff --git a/sdk/keyvault/azure-security-keyvault-jca/CHANGELOG.md b/sdk/keyvault/azure-security-keyvault-jca/CHANGELOG.md index b46d00a689526..f1c8d4dd9f90e 100644 --- a/sdk/keyvault/azure-security-keyvault-jca/CHANGELOG.md +++ b/sdk/keyvault/azure-security-keyvault-jca/CHANGELOG.md @@ -1,6 +1,6 @@ # Release History -## 2.7.0-beta.1 (Unreleased) +## 2.8.0-beta.1 (Unreleased) ### Features Added @@ -10,6 +10,11 @@ ### Other Changes +## 2.7.0 (2022-05-24) + +### Dependency Upgrades +Regular updates for dependency versions. + ## 2.6.0 (2022-02-25) ### Dependency Upgrades diff --git a/sdk/keyvault/azure-security-keyvault-jca/README.md b/sdk/keyvault/azure-security-keyvault-jca/README.md index c3a4e5e6175a4..432f689b4e727 100644 --- a/sdk/keyvault/azure-security-keyvault-jca/README.md +++ b/sdk/keyvault/azure-security-keyvault-jca/README.md @@ -50,7 +50,7 @@ add the direct dependency to your project as follows. com.azure azure-security-keyvault-jca - 2.6.0 + 2.7.0 ``` [//]: # ({x-version-update-end}) @@ -158,22 +158,22 @@ Or add permission by cli command: Please replace `${KEY_VAULT}` with your key vault name and replace `${MANAGED_IDENTITY}` with your principal's object-id. ### Supported key type -Content Type | Key Type | Key Size or Elliptic curve name | Sign algorithm | Support | --------------|----------|---------------------------------|---------------- |-------- | -PKCS #12 | RSA | 2048 | RSASSA-PSS | ✔ | -PKCS #12 | RSA | 3072 | RSASSA-PSS | ✔ | -PKCS #12 | RSA | 4096 | RSASSA-PSS | ✔ | -PKCS #12 | EC | P-256 | SHA256withECDSA | ✔ | -PKCS #12 | EC | P-384 | SHA384withECDSA | ✔ | -PKCS #12 | EC | P-521 | SHA512withECDSA | ✔ | -PKCS #12 | EC | P-256K | | ✘ | -PEM | RSA | 2048 | RSASSA-PSS | ✔ | -PEM | RSA | 3072 | RSASSA-PSS | ✔ | -PEM | RSA | 4096 | RSASSA-PSS | ✔ | -PEM | EC | P-256 | SHA256withECDSA | ✔ | -PEM | EC | P-384 | SHA384withECDSA | ✔ | -PEM | EC | P-521 | SHA512withECDSA | ✔ | -PEM | EC | P-256K | | ✘ | +| Content Type | Key Type | Key Size or Elliptic curve name | Sign algorithm | Support | +|--------------|----------|---------------------------------|-----------------|---------| +| PKCS #12 | RSA | 2048 | RSASSA-PSS | ✔ | +| PKCS #12 | RSA | 3072 | RSASSA-PSS | ✔ | +| PKCS #12 | RSA | 4096 | RSASSA-PSS | ✔ | +| PKCS #12 | EC | P-256 | SHA256withECDSA | ✔ | +| PKCS #12 | EC | P-384 | SHA384withECDSA | ✔ | +| PKCS #12 | EC | P-521 | SHA512withECDSA | ✔ | +| PKCS #12 | EC | P-256K | | ✘ | +| PEM | RSA | 2048 | RSASSA-PSS | ✔ | +| PEM | RSA | 3072 | RSASSA-PSS | ✔ | +| PEM | RSA | 4096 | RSASSA-PSS | ✔ | +| PEM | EC | P-256 | SHA256withECDSA | ✔ | +| PEM | EC | P-384 | SHA384withECDSA | ✔ | +| PEM | EC | P-521 | SHA512withECDSA | ✔ | +| PEM | EC | P-256K | | ✘ | ## Troubleshooting @@ -207,14 +207,18 @@ com.azure.security.keyvault.jca.level = ALL Azure Key Vault JCA clients raise exceptions. For example, if you try to check a client's identity with a certificate chain that does not include a trusted certificate, a `CertificateException` will be thrown. In the following snippet, the error is handled gracefully by catching the exception and displaying additional information about the error. ```java -try { - KeyVaultJcaProvider provider = new KeyVaultJcaProvider(); - Security.addProvider(provider); - ... - // Start SSL server socket - ... -} catch (CertificateException e) { - System.out.println(e.getMessage()); +class Demo { + void demo () { + try { + KeyVaultJcaProvider provider = new KeyVaultJcaProvider(); + Security.addProvider(provider); + // ... + // Start SSL server socket + // ... + } catch (CertificateException e) { + System.out.println(e.getMessage()); + } + } } ``` diff --git a/sdk/keyvault/azure-security-keyvault-jca/pom.xml b/sdk/keyvault/azure-security-keyvault-jca/pom.xml index 0ec0c7b5053dc..afc35dd93f664 100644 --- a/sdk/keyvault/azure-security-keyvault-jca/pom.xml +++ b/sdk/keyvault/azure-security-keyvault-jca/pom.xml @@ -14,7 +14,7 @@ com.azure azure-security-keyvault-jca - 2.7.0-beta.1 + 2.8.0-beta.1 JCA Provider for Azure Key Vault The Java Crypto Architecture (JCA) Provider for Azure Key Vault diff --git a/sdk/keyvault/azure-security-test-keyvault-jca/pom.xml b/sdk/keyvault/azure-security-test-keyvault-jca/pom.xml index 14fd26eed6834..a9d560260de34 100644 --- a/sdk/keyvault/azure-security-test-keyvault-jca/pom.xml +++ b/sdk/keyvault/azure-security-test-keyvault-jca/pom.xml @@ -25,7 +25,7 @@ com.azure azure-security-keyvault-jca - 2.7.0-beta.1 + 2.8.0-beta.1