PowerBuilder

Use Installed Cert on Windows for TLS Client Authentication

See more HTTP Examples

Demonstrates how to use a certificate that has already been installed on a Windows PC for TLS client authentication. PowerBuilder

integer li_rc
integer li_Success
oleobject loo_Http
oleobject loo_Cert

li_Success = 0

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

loo_Http = create oleobject
li_rc = loo_Http.ConnectToNewObject("Chilkat.Http")
if li_rc < 0 then
    destroy loo_Http
    MessageBox("Error","Connecting to COM object failed")
    return
end if

// On Windows, a pre-installed certificate can be loaded in a number of different ways.
// This example loads by the common name:
loo_Cert = create oleobject
li_rc = loo_Cert.ConnectToNewObject("Chilkat.Cert")

li_Success = loo_Cert.LoadByCommonName("My ECA Medium Assurance Identity Certificate")
if li_Success <> 1 then
    Write-Debug loo_Cert.LastErrorText
    destroy loo_Http
    destroy loo_Cert
    return
end if

// Make sure this certificate has a private key available.  
// It should be a private key such that when the certificate was installed, it was marked as "exportable"
// so that authorized programs are able to access the private key.
if loo_Cert.HasPrivateKey() <> 1 then
    Write-Debug "A private key is needed for TLS client authentication."
    Write-Debug "This certificate has no private key."
    destroy loo_Http
    destroy loo_Cert
    return
end if

// Set the certificate to be used for mutual TLS authentication
// (i.e. sets the client-side certificate for two-way TLS authentication)
li_Success = loo_Http.SetSslClientCert(loo_Cert)
if li_Success <> 1 then
    Write-Debug loo_Http.LastErrorText
    destroy loo_Http
    destroy loo_Cert
    return
end if

// At this point, the HTTP object instance is setup with the client-side cert, and any SSL/TLS
// connection will automatically use it if the server demands a client-side cert.


destroy loo_Http
destroy loo_Cert