Lianja

NTLM Client and Server Code

See more NTLM Examples

Demonstrates the NTLM authentication algorithm for both client and server. Lianja

llSuccess = .F.

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

loNtlmClient = createobject("CkNtlm")
loNtlmServer = createobject("CkNtlm")

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

loNtlmClient.Workstation = "MyWorkstation"
lcType1Msg = loNtlmClient.GenType1()

? "Type1 message from client to server:"
? lcType1Msg

// 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..
lcType1Info = loNtlmServer.ParseType1(lcType1Msg)

? "---"
? lcType1Info

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

lcType2Msg = loNtlmServer.GenType2(lcType1Msg)
if (loNtlmServer.LastMethodSuccess <> .T.) then
    ? loNtlmServer.LastErrorText
    release loNtlmClient
    release loNtlmServer
    return
endif

? "Type2 message from server to client:"
? lcType2Msg

// 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.
lcType2Info = loNtlmClient.ParseType2(lcType2Msg)

? "---"
? lcType2Info

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

lcType3Msg = loNtlmClient.GenType3(lcType2Msg)
if (loNtlmClient.LastMethodSuccess <> .T.) then
    ? loNtlmClient.LastErrorText
    release loNtlmClient
    release loNtlmServer
    return
endif

? "Type3 message from client to server:"
? lcType3Msg

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

llSuccess = loNtlmServer.LoadType3(lcType3Msg)
if (llSuccess <> .T.) then
    ? loNtlmServer.LastErrorText
    release loNtlmClient
    release loNtlmServer
    return
endif

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

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

// The server may generate the Type3 message again, using the client's correct
// password:
lcExpectedType3Msg = loNtlmServer.GenType3(lcType2Msg)

? "Expected Type3 Message:"
? lcExpectedType3Msg

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


release loNtlmClient
release loNtlmServer