SQL Server
SQL Server
Export a Traditional Private Key as Encoded Text
See more Private Key Examples
Demonstrates the Chilkat PrivateKey.GetPkcs1ENC method, which exports the key as the traditional/preferred unencrypted DER and encodes the DER bytes as text. The only argument names the binary encoding, such as base64 or hex.
Note: The file paths are relative to the application's current working directory. Absolute paths may also be used. Supply the paths appropriate to your own environment.
Background: This is the encoded-text form of the traditional DER representation — the same bytes the traditional PEM wraps, but returned as a string in the encoding you choose. Use it when a legacy consumer needs the traditional key structure delivered as text rather than as a PEM file. The DER is unencrypted, so the result is sensitive.
Chilkat SQL Server Downloads
-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
DECLARE @hr int
DECLARE @iTmp0 int
DECLARE @sTmp0 nvarchar(4000)
DECLARE @success int
SELECT @success = 0
-- Load a private key to export.
DECLARE @privKey int
EXEC @hr = sp_OACreate 'Chilkat.PrivateKey', @privKey OUT
IF @hr <> 0
BEGIN
PRINT 'Failed to create ActiveX component'
RETURN
END
EXEC sp_OAMethod @privKey, 'LoadPemFile', @success OUT, 'qa_data/private.pem'
IF @success = 0
BEGIN
EXEC sp_OAGetProperty @privKey, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @privKey
RETURN
END
-- Export as the traditional/preferred unencrypted DER, then encode the DER bytes as text. The
-- only argument names the binary encoding, such as "base64" or "hex".
DECLARE @encoded nvarchar(4000)
EXEC sp_OAMethod @privKey, 'GetPkcs1ENC', @encoded OUT, 'base64'
EXEC sp_OAGetProperty @privKey, 'LastMethodSuccess', @iTmp0 OUT
IF @iTmp0 = 0
BEGIN
EXEC sp_OAGetProperty @privKey, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @privKey
RETURN
END
PRINT @encoded
EXEC @hr = sp_OADestroy @privKey
END
GO