(AutoIt) Accept TLS Connection with Client Authentication

Demonstrates how to accept a TLS connection requiring client authentication. This is the case where the TLS client sends a certificate. It is also known as "Two-Way SSL".

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.

$oListenSslSocket = ObjCreate("Chilkat.Socket")

; An SSL/TLS server needs a digital certificate.  This example loads it from a PFX file.
; Note: This is the server's certificate.

$oCert = ObjCreate("Chilkat.Cert")
; The 1st argument is the file path, the 2nd arg is the 
; PFX file's password:
Local $bSuccess = $oCert.LoadPfxFile("chilkat.pfx","test")
If ($bSuccess <> True) Then
    ConsoleWrite($oCert.LastErrorText & @CRLF)
    Exit
EndIf

; To accept client client certificates in the TLS handshake,
; we must indicate a list of acceptable client certificate root CA DN's
; that are allowed.  (DN is an acronym for Distinguished Name.)
; Call AddSslAcceptableClientCaDn once for each acceptable CA DN.
; Here are a few examples so you can see the general format of a DN.
$oListenSslSocket.AddSslAcceptableClientCaDn("C=SE, O=AddTrust AB, OU=AddTrust External TTP Network, CN=AddTrust External CA Root")
$oListenSslSocket.AddSslAcceptableClientCaDn("O=Digital Signature Trust Co., CN=DST Root CA X3")

; Use the certificate:
$bSuccess = $oListenSslSocket.InitSslServer($oCert)
If ($bSuccess <> True) Then
    ConsoleWrite($oListenSslSocket.LastErrorText & @CRLF)
    Exit
EndIf

; Bind and listen on a port:
Local $iMyPort = 8123
; Allow for a max of 5 queued connect requests.
Local $iBackLog = 5
$bSuccess = $oListenSslSocket.BindAndListen($iMyPort,$iBackLog)
If ($bSuccess <> True) Then
    ConsoleWrite($oListenSslSocket.LastErrorText & @CRLF)
    Exit
EndIf

; If accepting an SSL/TLS connection, the SSL handshake is part of the connection
; establishment process. This involves a few back-and-forth messages between the 
; client and server to establish algorithms and a shared key to create the secure 
; channel. The sending and receiving of these messages are governed by the 
; MaxReadIdleMs and MaxSendIdleMs properties. If these properties are set to 0 
; (and this is the default unless changed by your application), then the 
; AcceptNextConnection can hang indefinitely during the SSL handshake process. 
; Make sure these properties are set to appropriate values before calling AcceptNextConnection.

; Set a 10 second max for waiting to read/write.  This is for the SSL/TLS handshake establishment.
$oListenSslSocket.MaxReadIdleMs = 10000
$oListenSslSocket.MaxSendIdleMs = 10000

; Accept a single client connection and establish the secure SSL/TLS channel:
Local $oClientSock
Local $iMaxWaitMillisec = 20000
$oClientSock = $oListenSslSocket.AcceptNextConnection($iMaxWaitMillisec)
If ($oListenSslSocket.LastMethodSuccess = False) Then
    ConsoleWrite($oListenSslSocket.LastErrorText & @CRLF)
    Exit
EndIf

; The client (in this example) is going to send a "Hello Server! -EOM-" 
; message.  Read it:
Local $sReceivedMsg = $oClientSock.ReceiveUntilMatch("-EOM-")
If ($oClientSock.LastMethodSuccess <> True) Then
    ConsoleWrite($oClientSock.LastErrorText & @CRLF)
    Exit
EndIf

ConsoleWrite($sReceivedMsg & @CRLF)

; Send a "Hello Client! -EOM-" message:
$bSuccess = $oClientSock.SendString("Hello Client! -EOM-")
If ($bSuccess <> True) Then
    ConsoleWrite($oClientSock.LastErrorText & @CRLF)
    Exit
EndIf

; Close the connection with the client
; Wait a max of 20 seconds (20000 millsec)
$bSuccess = $oClientSock.Close(20000)