NTLM Client and Server Code

Demonstrates the NTLM authentication algorithm for both client and server.

Download Chilkat .NET for 4.0 Framework

Download Chilkat .NET for 64-bit 4.0 Framework (x64)

Download Chilkat .NET for 2.0 / 3.5 Framework

Download Chilkat .NET for 64-bit 2.0 / 3.5 Framework (x64)

Download Chilkat .NET for 1.0 / 1.1 Framework

Chilkat.Ntlm ntlmClient = new Chilkat.Ntlm();

bool success;
success = ntlmClient.UnlockComponent("Anything for 30-day trial");
if (success != true) {
    textBox1.Text += ntlmClient.LastErrorText + "\r\n";
    return;
}

//  UnlockComponent only needs to be called once on the 1st object instance.

Chilkat.Ntlm ntlmServer = new Chilkat.Ntlm();

//  The NTLM protocol begins by the client sending the server
//  a Type1 message.
string type1Msg;
ntlmClient.Workstation = "MyWorkstation";
type1Msg = ntlmClient.GenType1();

textBox1.Text += "Type1 message from client to server:" + "\r\n";
textBox1.Text += type1Msg + "\r\n";

//  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..
string type1Info;
type1Info = ntlmServer.ParseType1(type1Msg);

textBox1.Text += "---" + "\r\n";
textBox1.Text += type1Info + "\r\n";

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

string type2Msg;
type2Msg = ntlmServer.GenType2(type1Msg);
if (type2Msg == null ) {
    textBox1.Text += ntlmServer.LastErrorText + "\r\n";
    return;
}

textBox1.Text += "Type2 message from server to client:" + "\r\n";
textBox1.Text += type2Msg + "\r\n";

//  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.
string type2Info;
type2Info = ntlmClient.ParseType2(type2Msg);

textBox1.Text += "---" + "\r\n";
textBox1.Text += type2Info + "\r\n";

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

string type3Msg;
type3Msg = ntlmClient.GenType3(type2Msg);
if (type3Msg == null ) {
    textBox1.Text += ntlmClient.LastErrorText + "\r\n";
    return;
}

textBox1.Text += "Type3 message from client to server:" + "\r\n";
textBox1.Text += type3Msg + "\r\n";

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

success = ntlmServer.LoadType3(type3Msg);
if (success != true) {
    textBox1.Text += ntlmServer.LastErrorText + "\r\n";
    return;
}

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

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

//  The server may generate the Type3 message again, using the client's correct
//  password:
string expectedType3Msg;
expectedType3Msg = ntlmServer.GenType3(type2Msg);

textBox1.Text += "Expected Type3 Message:" + "\r\n";
textBox1.Text += expectedType3Msg + "\r\n";

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