(PowerBuilder) 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.

Chilkat ActiveX Downloads

ActiveX for 32-bit and 64-bit Windows

integer li_rc
oleobject loo_Cert
integer li_Success

loo_Cert = create oleobject
// Use "Chilkat_9_5_0.Cert" for versions of Chilkat < 10.0.0
li_rc = loo_Cert.ConnectToNewObject("Chilkat.Cert")
if li_rc < 0 then
    destroy loo_Cert
    MessageBox("Error","Connecting to COM object failed")
    return
end if

// If you know the smart card PIN, it's good to set it prior to loading from the smartcard/USB token.
loo_Cert.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.
li_Success = loo_Cert.LoadFromSmartcard("")
if li_Success = 0 then
    Write-Debug loo_Cert.LastErrorText
    Write-Debug "Certificate not loaded."
    destroy loo_Cert
    return
end if

// 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.
Write-Debug loo_Cert.LastErrorText

Write-Debug "Found: " + loo_Cert.SubjectDN + " serial=" + loo_Cert.SerialNumber


destroy loo_Cert