(SQL Server) Convert Java KeyStore to PKCS12 / PFX

Loads a Java keystore file and saves it as a PKCS12 / PFX. A Java keystore (JKS) can contain two types of entries: (1) trusted root certificates or (2) private keys + cert chains. Usually a JKS will contain all entries of one type or another (and thus a particular JKS serves one purpose or another; meaning that a JKS containing trusted roots is used as a source for verifying pre-trusted roots, and a JKS containing private keys (and cert chains) is used as a secure, encrypted store for private keys).

A PKCS12 / PFX typically contains one or more private keys, along with each private key's certificate chain. Therefore, it typically makes sense to only write the private key entries to a PKCS12 (and the associated certificate chains). If a JKS contains trusted root certificates, it makes more sense to conver it to a PEM file (such as the CA cert bundle in PEM format from mozilla.org).

Chilkat ActiveX Downloads ActiveX for 32-bit and 64-bit Windows

-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    -- Important: Do not use nvarchar(max).  See the warning about using nvarchar(max).
    DECLARE @sTmp0 nvarchar(4000)
    -- This requires the Chilkat API to have been previously unlocked.
    -- See Global Unlock Sample for sample code.

    DECLARE @jks int
    -- Use "Chilkat_9_5_0.JavaKeyStore" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.JavaKeyStore', @jks OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    DECLARE @jksPassword nvarchar(4000)
    SELECT @jksPassword = 'myJksPassword'

    -- Load the Java keystore from a file.  The JKS file password is used
    -- to verify the keyed digest that is found at the very end of the keystore.
    -- It verifies that the keystore has not been modified.
    DECLARE @success int
    EXEC sp_OAMethod @jks, 'LoadFile', @success OUT, @jksPassword, '/someDir/keyStore.jks'
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @jks, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @jks
        RETURN
      END

    -- To convert, we'll access the private key entries
    -- from the JKS, add each to the PKCS12, and then save the PKCS12.
    DECLARE @pkcs12 int
    -- Use "Chilkat_9_5_0.Pfx" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.Pfx', @pkcs12 OUT

    DECLARE @numPrivateKeys int
    EXEC sp_OAGetProperty @jks, 'NumPrivateKeys', @numPrivateKeys OUT
    DECLARE @i int

    DECLARE @privKey int

    DECLARE @certChain int

    -- For each private key entry, get the private key and
    -- the associated certificate chain.
    -- Each private key is password protected.  Usually it is the same
    -- password as used for the keyed digest of the entire JKS.  
    -- However, this does not have to be.  The password is passed
    -- here to handle the possibility of each private key requiring
    -- a different password.
    SELECT @i = 0
    WHILE @i < @numPrivateKeys
      BEGIN
        EXEC sp_OAMethod @jks, 'GetPrivateKey', @privKey OUT, @jksPassword, @i
        EXEC sp_OAMethod @jks, 'GetPrivateKeyAlias', @sTmp0 OUT, @i
        PRINT @sTmp0
        EXEC sp_OAMethod @jks, 'GetCertChain', @certChain OUT, @i

        -- Add the private key and it's associated certificate chain to the PKCS12.
        EXEC sp_OAMethod @pkcs12, 'AddPrivateKey', @success OUT, @privKey, @certChain
        IF @success <> 1
          BEGIN
            EXEC sp_OAGetProperty @pkcs12, 'LastErrorText', @sTmp0 OUT
            PRINT @sTmp0
            EXEC @hr = sp_OADestroy @certChain

            EXEC @hr = sp_OADestroy @privKey

            EXEC @hr = sp_OADestroy @jks
            EXEC @hr = sp_OADestroy @pkcs12
            RETURN
          END

        EXEC @hr = sp_OADestroy @certChain

        EXEC @hr = sp_OADestroy @privKey

        SELECT @i = @i + 1
      END

    -- Save the PKCS12 / PFX to a file.
    -- The password can be the same as the JKS password, or something new.
    -- (With the PKCS12 format, there is a single password for the entire contents
    -- of the file.  With the JKS format, there is flexibility in allowing each private key
    -- to have it's own password.)
    DECLARE @pkcs12Password nvarchar(4000)
    SELECT @pkcs12Password = 'myNewPassword'
    EXEC sp_OAMethod @pkcs12, 'ToFile', @success OUT, @pkcs12Password, '/pkcs12_files/myPfx.p12'
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @pkcs12, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
      END
    ELSE
      BEGIN

        PRINT 'Successfully saved to PKCS12 format.'
      END

    EXEC @hr = sp_OADestroy @jks
    EXEC @hr = sp_OADestroy @pkcs12


END
GO