Uploaded image for project: 'EJBCA'
  1. EJBCA
  2. ECA-7278

Initial support for Azure Key Vault as EJBCA Crypto Token

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: EJBCA 7.3.0
    • Component/s: None
    • Labels:
      None
    • Provenance:
      Internal Delivery
    • Sprint:
      EJBCA Team Bob - 2019 w31, EJBCA Team Bob - 2019 w34

      Description

      In order to run EJBCA/SignServer in the Azure cloud, using their Key Vault cloud HSM, we need to implement a new Crypto Token. The Azure Key Vault does not use PKCS#11, but a REST API.

      https://docs.microsoft.com/en-us/rest/api/keyvault/

      Jamie Hablutzel, hablutzel1@gmail.com, has provided an initial patch for a crypto token accessing keys in the Azure Key Vault.

      A signature Provider is included which will let Java create digital signatures using the standard JCE framework.

        Attachments

        1. azure-keyvault-v10.patch
          82 kB
          Tomas Gustavsson
        2. azure-keyvault-v12.patch
          79 kB
          Tomas Gustavsson
        3. azure-keyvault-v13.patch
          85 kB
          Tomas Gustavsson
        4. azure-keyvault-v3.patch
          61 kB
          Tomas Gustavsson
        5. azure-keyvault-v5.patch
          75 kB
          Tomas Gustavsson
        6. azure-keyvault-v7.patch
          79 kB
          Tomas Gustavsson
        7. azure-keyvault-v9.patch
          81 kB
          Tomas Gustavsson
        8. Integration_with_Azure_Key_Vault_v2.patch
          53 kB
          Jaime Hablutzel
        9. Integration_with_Azure_Key_Vault.patch
          55 kB
          Tomas Gustavsson

          Issue Links

            Activity

              People

              Assignee:
              tomas Tomas Gustavsson
              Reporter:
              hablutzel1 Jaime Hablutzel
              Verified by:
              Jekaterina Bunina, Samuel Lidén Borell
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 2 weeks
                  2w
                  Remaining:
                  Time Spent - 1 week, 3 days, 1 hour, 30 minutes Remaining Estimate - 1 day, 6 hours, 30 minutes
                  1d 6h 30m
                  Logged:
                  Time Spent - 1 week, 3 days, 1 hour, 30 minutes Remaining Estimate - 1 day, 6 hours, 30 minutes
                  1w 3d 1h 30m