Certificate Management - Certificate Store Interface

Cryptlib utilizes commercial-strength RDBMS' to store keys in the internationally standardised X.509 format. The certificate store integrates seamlessly into existing databases and can be managed using existing tools. For example a key database stored on an MS SQL Server might be managed using Visual Basic or MS Access; a key database stored on an Oracle server might be managed through SQL*Plus.

Cryptlib can also store and retrieve certificates from LDAP directories, with optional SSL protection of the connection to the directory, as well as providing HTTP access to keys stored on the web.

Sample code which illustrates retrieving the public key for "John Doe" from a key database and the corresponding private key from a smart card is:

/* Get the public key certificate for a given user from a key database */ cryptKeysetOpen( &cryptKeyset, CRYPT_UNUSED, CRYPT_KEYSET_ODBC, "Public Keys", CRYPT_KEYSET_READONLY ); cryptGetPublicKey( cryptKeyset, &cryptCertificate, CRYPT_KEYID_NAME, "John Doe" ); cryptKeysetClose( cryptKeyset ); /* Use the private key for a given user stored in a smart card */ cryptDeviceOpen( &cryptDevice, CRYPT_UNUSED, CRYPT_DEVICE_PKCS11, "Gemplus" ); cryptGetPrivateKey( cryptDevice, &cryptPrivateKey, CRYPT_KEYID_NAME, "John Doe", NULL ); cryptDeviceClose( cryptDevice );

The key loaded into cryptCertificate and cryptPrivateKey can then be pushed into an envelope or secure session for use with the Cryptlib programming interface, or used with Cryptlib's certificate management functions.