Sample code for 30+ languages & platforms
Rust

PKCS11 Certificate Chain

See more PKCS11 Examples

Demonstrates how to make CA certs available for the certificate chain to be included when creating a signature (using a PKCS11 compatible smart card / USB token) such as for PDF, XMLDSig, etc.

Note: This example requires Chilkat v9.5.0.88 or later.

Chilkat Rust Downloads

Rust

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

// Note: Chilkat's PKCS11 implementation runs on Windows, Linux, Mac OS X, and other supported operating systems.

let pkcs11 = chilkat::Pkcs11::new();

// You will use the DLL (or shared lib) provided by your smart card vendor, or a DLL compatible with your smart card.
// On Windows, if the DLL is located in C:\Windows\System32, specify only the filename.
// Otherwise provide the full path.
pkcs11.set_shared_lib_path("bit4xpki.dll");

if pkcs11.initialize().is_err() {
    println!("{}", pkcs11.last_error_text());
    return;
}

// Pass -1 for the slotID to open a session on the first non-empty slot.
let slot_id = -1;

// Open a session.
let read_write = true;
if pkcs11.open_session(slot_id, read_write).is_err() {
    println!("{}", pkcs11.last_error_text());
    return;
}

// Make it an authenticated session by calling Login.
let user_type = 1;
// Make sure to use the correct PIN for your smart card..
let pin = "0000".to_string();
if pkcs11.login(user_type, &pin).is_err() {
    println!("{}", pkcs11.last_error_text());
    let _ = pkcs11.close_session().is_ok();
    return;
}

// Get the certificate (on the smart card) that has a private key.
let cert = chilkat::Cert::new();
if pkcs11.find_cert("privateKey", "", &cert).is_ok() {
    println!("Cert with private key: {}", cert.subject_cn());
} else {
    println!("No certificates having a private key were found.");
    let _ = pkcs11.close_session().is_ok();
    return;
}

// If the certificates in the chain of authentication were contained on the smart card,
// then Chilkat would already have them (via the FindCert function) and the certs in the chain will be automatically used
// as needed when signing occurs.

// If you have CA certs located elsewhere, such as in .cer files, you can make them available to Chilkat in the following way:

let cert_vault = chilkat::XmlCertVault::new();
// Please review the methods available in the XML certificate vault class.  Different methods exist for adding certificates
// from various sources, such as PEM, PFX, or in-memory sources..
let _ = cert_vault.add_cert_file("someDir/caIntermediateCert.cer").is_ok();
// ...
let _ = cert_vault.add_cert_file("someDir/caCert.cer").is_ok();
// (Your code should check the return value to make sure it succeeded.)

if cert.use_cert_vault(&cert_vault).is_err() {
    println!("{}", cert.last_error_text());
    let _ = pkcs11.close_session().is_ok();
    return;
}

// --------------------------------------------------------------------------
// At this point, we have the cert (and certs in the chain of authentication) to be used for signing.
// The code for using the certificate in creating the digital signature, such as for a PDF, XML, etc., go here...

// --------------------------------------------------------------------------

// Revert to an unauthenticated session by calling Logout.
if pkcs11.logout().is_err() {
    println!("{}", pkcs11.last_error_text());
    let _ = pkcs11.close_session().is_ok();
    return;
}

// When finished, close the session.
// It is important to close the session (memory leaks will occur if the session is not properly closed).
if pkcs11.close_session().is_err() {
    println!("{}", pkcs11.last_error_text());
    return;
}

println!("Success.");