Chilkat HOME .NET Core C# Android™ AutoIt C C# C++ Chilkat2-Python CkPython Classic ASP DataFlex Delphi ActiveX Delphi DLL Go Java Lianja Mono C# Node.js Objective-C PHP ActiveX PHP Extension Perl PowerBuilder PowerShell PureBasic Ruby SQL Server Swift 2 Swift 3,4,5... Tcl Unicode C Unicode C++ VB.NET VBScript Visual Basic 6.0 Visual FoxPro Xojo Plugin
(C) NTLM Client and Server CodeDemonstrates the NTLM authentication algorithm for both client and server.
#include <C_CkNtlm.h> void ChilkatSample(void) { HCkNtlm ntlmClient; HCkNtlm ntlmServer; const char *type1Msg; const char *type1Info; const char *type2Msg; const char *type2Info; const char *type3Msg; BOOL success; const char *clientUsername; const char *expectedType3Msg; // This example assumes the Chilkat API to have been previously unlocked. // See Global Unlock Sample for sample code. ntlmClient = CkNtlm_Create(); ntlmServer = CkNtlm_Create(); // The NTLM protocol begins by the client sending the server // a Type1 message. CkNtlm_putWorkstation(ntlmClient,"MyWorkstation"); type1Msg = CkNtlm_genType1(ntlmClient); printf("Type1 message from client to server:\n"); printf("%s\n",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.. type1Info = CkNtlm_parseType1(ntlmServer,type1Msg); printf("---\n"); printf("%s\n",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). CkNtlm_putTargetName(ntlmServer,"myAuthRealm"); type2Msg = CkNtlm_genType2(ntlmServer,type1Msg); if (CkNtlm_getLastMethodSuccess(ntlmServer) != TRUE) { printf("%s\n",CkNtlm_lastErrorText(ntlmServer)); CkNtlm_Dispose(ntlmClient); CkNtlm_Dispose(ntlmServer); return; } printf("Type2 message from server to client:\n"); printf("%s\n",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. type2Info = CkNtlm_parseType2(ntlmClient,type2Msg); printf("---\n"); printf("%s\n",type2Info); // The client will now generate the final Type3 message to be sent to the server. // This requires the Username and Password: CkNtlm_putUserName(ntlmClient,"test123"); CkNtlm_putPassword(ntlmClient,"myPassword"); type3Msg = CkNtlm_genType3(ntlmClient,type2Msg); if (CkNtlm_getLastMethodSuccess(ntlmClient) != TRUE) { printf("%s\n",CkNtlm_lastErrorText(ntlmClient)); CkNtlm_Dispose(ntlmClient); CkNtlm_Dispose(ntlmServer); return; } printf("Type3 message from client to server:\n"); printf("%s\n",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. success = CkNtlm_LoadType3(ntlmServer,type3Msg); if (success != TRUE) { printf("%s\n",CkNtlm_lastErrorText(ntlmServer)); CkNtlm_Dispose(ntlmClient); CkNtlm_Dispose(ntlmServer); return; } // The Username property now contains the username that was embedded within // the Type3 message. It can be used to lookup the password. clientUsername = CkNtlm_userName(ntlmServer); // For this example, we'll simply set the password to a literal string: CkNtlm_putPassword(ntlmServer,"myPassword"); // The server may generate the Type3 message again, using the client's correct // password: expectedType3Msg = CkNtlm_genType3(ntlmServer,type2Msg); printf("Expected Type3 Message:\n"); printf("%s\n",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 CkNtlm_Dispose(ntlmClient); CkNtlm_Dispose(ntlmServer); } |
© 2000-2024 Chilkat Software, Inc. All Rights Reserved.