(AutoIt) Use Installed Cert on Windows for TLS Client Authentication

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

Chilkat ActiveX Downloads ActiveX for 32-bit and 64-bit Windows

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

$oHttp = ObjCreate("Chilkat.Http")

Local $bSuccess

; On Windows, a pre-installed certificate can be loaded in a number of different ways.
; This example loads by the common name:
$oCert = ObjCreate("Chilkat.Cert")
Local $bSuccess = $oCert.LoadByCommonName("My ECA Medium Assurance Identity Certificate")
If ($bSuccess <> True) Then
    ConsoleWrite($oCert.LastErrorText & @CRLF)
    Exit
EndIf

; 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 ($oCert.HasPrivateKey() <> True) Then
    ConsoleWrite("A private key is needed for TLS client authentication." & @CRLF)
    ConsoleWrite("This certificate has no private key." & @CRLF)
    Exit
EndIf

; Set the certificate to be used for mutual TLS authentication
; (i.e. sets the client-side certificate for two-way TLS authentication)
$bSuccess = $oHttp.SetSslClientCert($oCert)
If ($bSuccess <> True) Then
    ConsoleWrite($oHttp.LastErrorText & @CRLF)
    Exit
EndIf

; 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.