Java

Load Default Certificate from Smart Card or Token

See more Certificates Examples

Chilkat contains internal logic to examine a connected smart card or USB token, and will make decisions based on make/model to successfully interact with the hardware. When faced with a new smartcard or token, the best starting point is to call LoadFromSmartcard with an empty string argument to see what Chilkat discovers. Java

import com.chilkatsoft.*;

public class ChilkatExample {

  static {
    try {
        System.loadLibrary("chilkat");
    } catch (UnsatisfiedLinkError e) {
      System.err.println("Native code library failed to load.\n" + e);
      System.exit(1);
    }
  }

  public static void main(String argv[])
  {
    boolean success = false;

    CkCert cert = new CkCert();

    // If you know the smart card PIN, it's good to set it prior to loading from the smartcard/USB token.
    cert.put_SmartCardPin("12345678");

    // To let Chilkat discover what smartcard or token is connected, pass an empty string to LoadFromSmartcard.
    // When testing in this way, it's best to have only a single smartcard or token connected to the system.
    success = cert.LoadFromSmartcard("");
    if (success == false) {
        System.out.println(cert.lastErrorText());
        System.out.println("Certificate not loaded.");
        return;
        }

    // The LastErrorText property on all Chilkat objects will contain 
    // information even when the method call is successful.
    // You can examine the LastErrorText to see what Chilkat found and
    // what decisions were made.
    // 
    // For example, if a certificate was successfully loaded via LoadFromSmartcard,
    // but then signing failed, such as w/ Pdf, XmlDSig, CAdES, etc.,
    // then we would want to examine the LastErrorText from the call to
    // LoadFromSmartcard to get detailed information about the card.
    System.out.println(cert.lastErrorText());

    System.out.println("Found: " + cert.subjectDN() + " serial=" + cert.serialNumber());
  }
}