SQL Server
SQL Server
Add a PFX Source to MailMan from BinData
See more POP3 Examples
Demonstrates the Chilkat MailMan.AddPfxSourceBd method, which adds a PFX/PKCS#12 certificate store to the MailMan object's internal list of sources used for locating certificates and private keys. The first argument is a BinData containing the PFX bytes and the second is the PFX password. This example loads a PFX into a BinData, registers it, and fetches a message Chilkat can decrypt.
Background: This is the in-memory (
BinData) counterpart to AddPfxSourceFile. It is the right choice when the PFX bytes come from somewhere other than a file — a database, a secrets manager, or an HTTPS download — letting you supply the certificate and private key without first writing sensitive key material to disk.Chilkat SQL Server Downloads
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
DECLARE @hr int
DECLARE @iTmp0 int
DECLARE @sTmp0 nvarchar(4000)
DECLARE @success int
SELECT @success = 0
-- Demonstrates the MailMan.AddPfxSourceBd method, which adds a PFX/PKCS#12 certificate store
-- to the MailMan object's internal list of sources used for locating certificates and
-- private keys. The 1st argument is a BinData containing the PFX bytes and the 2nd is the
-- PFX password.
DECLARE @mailman int
EXEC @hr = sp_OACreate 'Chilkat.MailMan', @mailman OUT
IF @hr <> 0
BEGIN
PRINT 'Failed to create ActiveX component'
RETURN
END
-- Configure the POP3 server connection.
EXEC sp_OASetProperty @mailman, 'MailHost', 'pop.example.com'
EXEC sp_OASetProperty @mailman, 'MailPort', 995
EXEC sp_OASetProperty @mailman, 'PopSsl', 1
EXEC sp_OASetProperty @mailman, 'PopUsername', 'user@example.com'
EXEC sp_OASetProperty @mailman, 'PopPassword', 'myPassword'
-- Load the PFX bytes into a BinData (they could come from a file, database, or secrets store).
DECLARE @bdPfx int
EXEC @hr = sp_OACreate 'Chilkat.BinData', @bdPfx OUT
EXEC sp_OAMethod @bdPfx, 'LoadFile', @success OUT, 'qa_data/certs/decryption.pfx'
IF @success = 0
BEGIN
EXEC sp_OAGetProperty @bdPfx, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @mailman
EXEC @hr = sp_OADestroy @bdPfx
RETURN
END
-- Add the PFX as a source of certificates and private keys.
EXEC sp_OAMethod @mailman, 'AddPfxSourceBd', @success OUT, @bdPfx, 'pfx_password'
IF @success = 0
BEGIN
EXEC sp_OAGetProperty @mailman, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @mailman
EXEC @hr = sp_OADestroy @bdPfx
RETURN
END
-- Fetch a message; if it is encrypted, Chilkat can decrypt it using the PFX source.
DECLARE @email int
EXEC @hr = sp_OACreate 'Chilkat.Email', @email OUT
EXEC sp_OAMethod @mailman, 'FetchOne', @success OUT, 0, 0, 1, @email
IF @success = 0
BEGIN
EXEC sp_OAGetProperty @mailman, 'LastErrorText', @sTmp0 OUT
PRINT @sTmp0
EXEC @hr = sp_OADestroy @mailman
EXEC @hr = sp_OADestroy @bdPfx
EXEC @hr = sp_OADestroy @email
RETURN
END
EXEC sp_OAGetProperty @email, 'Decrypted', @iTmp0 OUT
PRINT 'Decrypted = ' + @iTmp0
-- Note: The path "qa_data/certs/decryption.pfx" is a relative local filesystem path,
-- relative to the current working directory of the running application.
-- Note: Explicitly connecting/authenticating is optional. Chilkat MailMan automatically
-- connects and authenticates -- using the property settings above -- whenever a server
-- operation requires it. Calling the explicit connect/authenticate methods can still be
-- helpful to determine whether a failure occurs while connecting or while authenticating.
EXEC @hr = sp_OADestroy @mailman
EXEC @hr = sp_OADestroy @bdPfx
EXEC @hr = sp_OADestroy @email
END
GO