(AutoIt) NTLM Client and Server Code

Demonstrates the NTLM authentication algorithm for both client and server.

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

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

$oNtlmClient = ObjCreate("Chilkat.Ntlm")
$oNtlmServer = ObjCreate("Chilkat.Ntlm")

; The NTLM protocol begins by the client sending the server
; a Type1 message. 
Local $sType1Msg
$oNtlmClient.Workstation = "MyWorkstation"
$sType1Msg = $oNtlmClient.GenType1()

ConsoleWrite("Type1 message from client to server:" & @CRLF)
ConsoleWrite($sType1Msg & @CRLF)

; If the server wishes to examine the information embedded within the
; Type1 message, it may call ParseType1. 
; This step is not necessary, it is only for informational purposes..
Local $sType1Info = $oNtlmServer.ParseType1($sType1Msg)

ConsoleWrite("---" & @CRLF)
ConsoleWrite($sType1Info & @CRLF)

; The server now generates a Type2 message to be sent to the client.
; The Type2 message requires a TargetName.  A TargetName is
; the authentication realm in which the authenticating account
; has membership (a domain name for domain accounts, or server name
; for local machine accounts).
$oNtlmServer.TargetName = "myAuthRealm"

Local $sType2Msg = $oNtlmServer.GenType2($sType1Msg)
If ($oNtlmServer.LastMethodSuccess <> True) Then
    ConsoleWrite($oNtlmServer.LastErrorText & @CRLF)
    Exit
EndIf

ConsoleWrite("Type2 message from server to client:" & @CRLF)
ConsoleWrite($sType2Msg & @CRLF)

; The client may examine the information embedded in the Type2 message 
; by calling ParseType2, which returns XML.  This is only for informational purposes
; and is not required.
Local $sType2Info = $oNtlmClient.ParseType2($sType2Msg)

ConsoleWrite("---" & @CRLF)
ConsoleWrite($sType2Info & @CRLF)

; The client will now generate the final Type3 message to be sent to the server.
; This requires the Username and Password:
$oNtlmClient.UserName = "test123"
$oNtlmClient.Password = "myPassword"

Local $sType3Msg
$sType3Msg = $oNtlmClient.GenType3($sType2Msg)
If ($oNtlmClient.LastMethodSuccess <> True) Then
    ConsoleWrite($oNtlmClient.LastErrorText & @CRLF)
    Exit
EndIf

ConsoleWrite("Type3 message from client to server:" & @CRLF)
ConsoleWrite($sType3Msg & @CRLF)

; The server may verify the response by first "loading" the Type3 message.
; This sets the various properties such as Username, Domain, Workstation,
; and ClientChallenge to the values embedded within theType3 message.
; The server may then use the Username to lookup the password.  
; Looking up the password is dependent on your infrastructure.  Perhaps your
; usernames/passwords are stored in a secure database.  If that's the case, you would
; write code to issue a query to get the password string for the given username.
; Once the password is obtained, set the Password property and then 
; generate the Type3 response again.  If the server's Type3 response matches
; the client's Type3 response, then the client's password is correct.

Local $bSuccess = $oNtlmServer.LoadType3($sType3Msg)
If ($bSuccess <> True) Then
    ConsoleWrite($oNtlmServer.LastErrorText & @CRLF)
    Exit
EndIf

; The Username property now contains the username that was embedded within
; the Type3 message.  It can be used to lookup the password.
Local $sClientUsername = $oNtlmServer.UserName

; For this example, we'll simply set the password to a literal string:
$oNtlmServer.Password = "myPassword"

; The server may generate the Type3 message again, using the client's correct
; password:
Local $sExpectedType3Msg = $oNtlmServer.GenType3($sType2Msg)

ConsoleWrite("Expected Type3 Message:" & @CRLF)
ConsoleWrite($sExpectedType3Msg & @CRLF)

; If the Type3 message received from the client is exactly the same as the
; expected Type3 message, then the client must've used the same password,
; and authentication is successful