(Android™) NTLM Client and Server Code

Demonstrates the NTLM authentication algorithm for both client and server.

Chilkat Android™ Downloads Android™ Java Libraries Android C/C++ Libraries

// Important: Don't forget to include the call to System.loadLibrary
// as shown at the bottom of this code sample.
package com.test;

import android.app.Activity;
import com.chilkatsoft.*;

import android.widget.TextView;
import android.os.Bundle;

public class SimpleActivity extends Activity {

  private static final String TAG = "Chilkat";

  // Called when the activity is first created.
  @Override
  public void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);

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

    CkNtlm ntlmClient = new CkNtlm();
    CkNtlm ntlmServer = new CkNtlm();

    // The NTLM protocol begins by the client sending the server
    // a Type1 message. 
    String type1Msg;
    ntlmClient.put_Workstation("MyWorkstation");
    type1Msg = ntlmClient.genType1();

    Log.i(TAG, "Type1 message from client to server:");
    Log.i(TAG, 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..
    String type1Info = ntlmServer.parseType1(type1Msg);

    Log.i(TAG, "---");
    Log.i(TAG, 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).
    ntlmServer.put_TargetName("myAuthRealm");

    String type2Msg = ntlmServer.genType2(type1Msg);
    if (ntlmServer.get_LastMethodSuccess() != true) {
        Log.i(TAG, ntlmServer.lastErrorText());
        return;
        }

    Log.i(TAG, "Type2 message from server to client:");
    Log.i(TAG, 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.
    String type2Info = ntlmClient.parseType2(type2Msg);

    Log.i(TAG, "---");
    Log.i(TAG, type2Info);

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

    String type3Msg;
    type3Msg = ntlmClient.genType3(type2Msg);
    if (ntlmClient.get_LastMethodSuccess() != true) {
        Log.i(TAG, ntlmClient.lastErrorText());
        return;
        }

    Log.i(TAG, "Type3 message from client to server:");
    Log.i(TAG, 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.

    boolean success = ntlmServer.LoadType3(type3Msg);
    if (success != true) {
        Log.i(TAG, ntlmServer.lastErrorText());
        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 = ntlmServer.userName();

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

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

    Log.i(TAG, "Expected Type3 Message:");
    Log.i(TAG, 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

  }

  static {
      System.loadLibrary("chilkat");

      // Note: If the incorrect library name is passed to System.loadLibrary,
      // then you will see the following error message at application startup:
      //"The application <your-application-name> has stopped unexpectedly. Please try again."
  }
}