Chilkat Examples

ChilkatHOMEAndroid™Classic ASPCC++C#Mono C#.NET Core C#C# UWP/WinRTDataFlexDelphi ActiveXDelphi DLLVisual FoxProJavaLianjaMFCObjective-CPerlPHP ActiveXPHP ExtensionPowerBuilderPowerShellPureBasicCkPythonChilkat2-PythonRubySQL ServerSwift 2Swift 3,4,5...TclUnicode CUnicode C++Visual Basic 6.0VB.NETVB.NET UWP/WinRTVBScriptXojo PluginNode.jsExcelGo

SQL Server Examples

Web API Categories

ASN.1
Amazon EC2
Amazon Glacier
Amazon S3
Amazon S3 (new)
Amazon SES
Amazon SNS
Amazon SQS
Async
Azure Cloud Storage
Azure Service Bus
Azure Table Service
Base64
Bounced Email
Box
CAdES
CSR
CSV
Certificates
Compression
DKIM / DomainKey
DSA
Diffie-Hellman
Digital Signatures
Dropbox
Dynamics CRM
EBICS
ECC
Ed25519
Email Object
Encryption
FTP
FileAccess
Firebase
GMail REST API
GMail SMTP/IMAP/POP
Geolocation
Google APIs
Google Calendar
Google Cloud SQL
Google Cloud Storage
Google Drive
Google Photos
Google Sheets
Google Tasks
Gzip
HTML-to-XML/Text
HTTP

HTTP Misc
IMAP
JSON
JSON Web Encryption (JWE)
JSON Web Signatures (JWS)
JSON Web Token (JWT)
Java KeyStore (JKS)
MHT / HTML Email
MIME
MS Storage Providers
Microsoft Graph
NTLM
OAuth1
OAuth2
OIDC
Office365
OneDrive
OpenSSL
Outlook
Outlook Calendar
Outlook Contact
PDF Signatures
PEM
PFX/P12
PKCS11
POP3
PRNG
REST
REST Misc
RSA
SCP
SCard
SFTP
SMTP
SSH
SSH Key
SSH Tunnel
ScMinidriver
SharePoint
Socket/SSL/TLS
Spider
Stream
Tar Archive
Upload
WebSocket
XAdES
XML
XML Digital Signatures
XMP
Zip
curl

 

 

 

(SQL Server) 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

CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    DECLARE @iTmp0 int
    DECLARE @sTmp0 nvarchar(4000)
    -- This example assumes the Chilkat API to have been previously unlocked.
    -- See Global Unlock Sample for sample code.

    DECLARE @ntlmClient int
    EXEC @hr = sp_OACreate 'Chilkat_9_5_0.Ntlm', @ntlmClient OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    DECLARE @ntlmServer int
    EXEC @hr = sp_OACreate 'Chilkat_9_5_0.Ntlm', @ntlmServer OUT

    -- The NTLM protocol begins by the client sending the server
    -- a Type1 message. 
    DECLARE @type1Msg nvarchar(4000)

    EXEC sp_OASetProperty @ntlmClient, 'Workstation', 'MyWorkstation'
    EXEC sp_OAMethod @ntlmClient, 'GenType1', @type1Msg OUT


    PRINT 'Type1 message from client to server:'

    PRINT @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..
    DECLARE @type1Info nvarchar(4000)
    EXEC sp_OAMethod @ntlmServer, 'ParseType1', @type1Info OUT, @type1Msg


    PRINT '---'

    PRINT @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).
    EXEC sp_OASetProperty @ntlmServer, 'TargetName', 'myAuthRealm'

    DECLARE @type2Msg nvarchar(4000)
    EXEC sp_OAMethod @ntlmServer, 'GenType2', @type2Msg OUT, @type1Msg
    EXEC sp_OAGetProperty @ntlmServer, 'LastMethodSuccess', @iTmp0 OUT
    IF @iTmp0 <> 1
      BEGIN
        EXEC sp_OAGetProperty @ntlmServer, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @ntlmClient
        EXEC @hr = sp_OADestroy @ntlmServer
        RETURN
      END


    PRINT 'Type2 message from server to client:'

    PRINT @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.
    DECLARE @type2Info nvarchar(4000)
    EXEC sp_OAMethod @ntlmClient, 'ParseType2', @type2Info OUT, @type2Msg


    PRINT '---'

    PRINT @type2Info

    -- The client will now generate the final Type3 message to be sent to the server.
    -- This requires the Username and Password:
    EXEC sp_OASetProperty @ntlmClient, 'UserName', 'test123'
    EXEC sp_OASetProperty @ntlmClient, 'Password', 'myPassword'

    DECLARE @type3Msg nvarchar(4000)

    EXEC sp_OAMethod @ntlmClient, 'GenType3', @type3Msg OUT, @type2Msg
    EXEC sp_OAGetProperty @ntlmClient, 'LastMethodSuccess', @iTmp0 OUT
    IF @iTmp0 <> 1
      BEGIN
        EXEC sp_OAGetProperty @ntlmClient, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @ntlmClient
        EXEC @hr = sp_OADestroy @ntlmServer
        RETURN
      END


    PRINT 'Type3 message from client to server:'

    PRINT @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.

    DECLARE @success int
    EXEC sp_OAMethod @ntlmServer, 'LoadType3', @success OUT, @type3Msg
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @ntlmServer, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @ntlmClient
        EXEC @hr = sp_OADestroy @ntlmServer
        RETURN
      END

    -- The Username property now contains the username that was embedded within
    -- the Type3 message.  It can be used to lookup the password.
    DECLARE @clientUsername nvarchar(4000)
    EXEC sp_OAGetProperty @ntlmServer, 'UserName', @clientUsername OUT

    -- For this example, we'll simply set the password to a literal string:
    EXEC sp_OASetProperty @ntlmServer, 'Password', 'myPassword'

    -- The server may generate the Type3 message again, using the client's correct
    -- password:
    DECLARE @expectedType3Msg nvarchar(4000)
    EXEC sp_OAMethod @ntlmServer, 'GenType3', @expectedType3Msg OUT, @type2Msg


    PRINT 'Expected Type3 Message:'

    PRINT @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

    EXEC @hr = sp_OADestroy @ntlmClient
    EXEC @hr = sp_OADestroy @ntlmServer


END
GO

 

© 2000-2021 Chilkat Software, Inc. All Rights Reserved.