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

integer li_rc
oleobject loo_NtlmClient
oleobject loo_NtlmServer
string ls_Type1Msg
string ls_Type1Info
string ls_Type2Msg
string ls_Type2Info
string ls_Type3Msg
integer li_Success
string ls_ClientUsername
string ls_ExpectedType3Msg

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

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

// The NTLM protocol begins by the client sending the server
// a Type1 message. 

loo_NtlmClient.Workstation = "MyWorkstation"
ls_Type1Msg = loo_NtlmClient.GenType1()

Write-Debug "Type1 message from client to server:"
Write-Debug ls_Type1Msg

// 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..
ls_Type1Info = loo_NtlmServer.ParseType1(ls_Type1Msg)

Write-Debug "---"
Write-Debug ls_Type1Info

// 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).
loo_NtlmServer.TargetName = "myAuthRealm"

ls_Type2Msg = loo_NtlmServer.GenType2(ls_Type1Msg)
if loo_NtlmServer.LastMethodSuccess <> 1 then
    Write-Debug loo_NtlmServer.LastErrorText
    destroy loo_NtlmClient
    destroy loo_NtlmServer
    return
end if

Write-Debug "Type2 message from server to client:"
Write-Debug ls_Type2Msg

// 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.
ls_Type2Info = loo_NtlmClient.ParseType2(ls_Type2Msg)

Write-Debug "---"
Write-Debug ls_Type2Info

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

ls_Type3Msg = loo_NtlmClient.GenType3(ls_Type2Msg)
if loo_NtlmClient.LastMethodSuccess <> 1 then
    Write-Debug loo_NtlmClient.LastErrorText
    destroy loo_NtlmClient
    destroy loo_NtlmServer
    return
end if

Write-Debug "Type3 message from client to server:"
Write-Debug ls_Type3Msg

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

li_Success = loo_NtlmServer.LoadType3(ls_Type3Msg)
if li_Success <> 1 then
    Write-Debug loo_NtlmServer.LastErrorText
    destroy loo_NtlmClient
    destroy loo_NtlmServer
    return
end if

// The Username property now contains the username that was embedded within
// the Type3 message.  It can be used to lookup the password.
ls_ClientUsername = loo_NtlmServer.UserName

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

// The server may generate the Type3 message again, using the client's correct
// password:
ls_ExpectedType3Msg = loo_NtlmServer.GenType3(ls_Type2Msg)

Write-Debug "Expected Type3 Message:"
Write-Debug ls_ExpectedType3Msg

// 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


destroy loo_NtlmClient
destroy loo_NtlmServer