SQL Server

Duplicate Java HMAC-SHA1 using Chilkat

See more Encryption Examples

This example uses Chilkat to produce the same results as this Java code:

import org.apache.commons.codec.binary.Base64;
import org.apache.commons.codec.binary.Hex;

import javax.crypto.Mac;
import javax.crypto.spec.SecretKeySpec;
import java.security.InvalidKeyException;
import java.security.Key;
import java.security.NoSuchAlgorithmException;

public void hmacSignatureExample() throws NoSuchAlgorithmException,
InvalidKeyException {

final String method = "POST";
final Long epoch = 1456765639015L; // Hardcoding for this example
final String uri = "/api/v5/policy/1234567890";
final String newline = "\n";

final String privateKey = "qwfvUeVRWAwyjlAzGivefFPTg+m6QtBPmDVv7Ra
/u7K3UuVVRhrZ/qc8EPh8IGJatuxsWD4EX+D9qE/eVvLTpw==";
final String publicKey = "16baedbe244b6c063968850716afb319a";

// Prepare the signature
final String plainText = method + newline + epoch + newline + uri + newline;

// Hash the plaintext with the private key
final byte[] keyBytes = privateKey.getBytes();
final Key key = new SecretKeySpec(keyBytes, 0, keyBytes.length, "HmacSHA1");
final Mac mac = Mac.getInstance("HmacSHA1");
mac.init(key);
String signatureHash = new String(Hex.encodeHex(mac.doFinal(plainText.
getBytes())));

// Prefix with public key
signatureHash = publicKey + ":" + signatureHash;

// Base64 encode to produce AUTHORIZATION
final String authorization = new String(Base64.encodeBase64(signatureHash.
getBytes()));
}

SQL Server

-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    DECLARE @success int
    SELECT @success = 0

    -- This example assumes the Chilkat API to have been previously unlocked.
    -- See Global Unlock Sample for sample code.

    -- This is clearly in base64 encoding.
    DECLARE @privateKey nvarchar(4000)
    SELECT @privateKey = 'qwfvUeVRWAwyjlAzGivefFPTg+m6QtBPmDVv7Ra/u7K3UuVVRhrZ/qc8EPh8IGJatuxsWD4EX+D9qE/eVvLTpw=='

    -- This is clearly in the hex encoding.
    DECLARE @publicKey nvarchar(4000)
    SELECT @publicKey = '16baedbe244b6c063968850716afb319a'

    DECLARE @plainText nvarchar(4000)
    SELECT @plainText = 'POST' + CHAR(10) + '1456765639015' + CHAR(10) + '/api/v5/policy/1234567890' + CHAR(10)

    DECLARE @crypt int
    EXEC @hr = sp_OACreate 'Chilkat.Crypt2', @crypt OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    -- We want HMAC-SHA1.
    EXEC sp_OASetProperty @crypt, 'MacAlgorithm', 'HMAC'
    EXEC sp_OASetProperty @crypt, 'HashAlgorithm', 'SHA1'

    -- The Java code (above) is literally using the us-ascii chars of the base64 string as the HMAC key.
    -- (It is NOT using the base64 decoded bytes.)
    EXEC sp_OAMethod @crypt, 'SetMacKeyEncoded', @success OUT, @privateKey, 'us-ascii'

    -- We want our HMAC-SHA1 output to be a hex string.
    EXEC sp_OASetProperty @crypt, 'EncodingMode', 'hex_lower'

    DECLARE @hmacHex nvarchar(4000)
    EXEC sp_OAMethod @crypt, 'MacStringENC', @hmacHex OUT, @plainText


    PRINT @hmacHex

    -- The expected result is: dd3e8440f6b550f152156ea5e12d3e20b262adae

    DECLARE @sbSignatureHash int
    EXEC @hr = sp_OACreate 'Chilkat.StringBuilder', @sbSignatureHash OUT

    EXEC sp_OAMethod @sbSignatureHash, 'Append', @success OUT, @publicKey
    EXEC sp_OAMethod @sbSignatureHash, 'Append', @success OUT, ':'
    EXEC sp_OAMethod @sbSignatureHash, 'Append', @success OUT, @hmacHex

    DECLARE @authorization nvarchar(4000)
    EXEC sp_OAMethod @sbSignatureHash, 'GetEncoded', @authorization OUT, 'base64', 'utf-8'

    PRINT 'Authorization: ' + @authorization

    -- The expected result is:  MTZiYWVkYmUyNDRiNmMwNjM5Njg4NTA3MTZhZmIzMTlhOmRkM2U4NDQwZjZiNTUwZjE1MjE1NmVhNWUxMmQzZTIwYjI2MmFkYWU=

    EXEC @hr = sp_OADestroy @crypt
    EXEC @hr = sp_OADestroy @sbSignatureHash


END
GO