Chilkat Examples

ChilkatHOME.NET Core C#Android™AutoItCC#C++Chilkat2-PythonCkPythonClassic ASPDataFlexDelphi ActiveXDelphi DLLGoJavaLianjaMono C#Node.jsObjective-CPHP ActiveXPHP ExtensionPerlPowerBuilderPowerShellPureBasicRubySQL ServerSwift 2Swift 3,4,5...TclUnicode CUnicode C++VB.NETVBScriptVisual Basic 6.0Visual FoxProXojo Plugin

Swift 3,4,5... Examples

Web API Categories

ASN.1
AWS KMS
AWS Misc
Amazon EC2
Amazon Glacier
Amazon S3
Amazon S3 (new)
Amazon SES
Amazon SNS
Amazon SQS
Async
Azure Cloud Storage
Azure Key Vault
Azure Service Bus
Azure Table Service
Base64
Bounced Email
Box
CAdES
CSR
CSV
Certificates
Code Signing
Compression
DKIM / DomainKey
DNS
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
Misc
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
SharePoint Online
Signing in the Cloud
Socket/SSL/TLS
Spider
Stream
Tar Archive
ULID/UUID
Upload
WebSocket
XAdES
XML
XML Digital Signatures
XMP
Zip
curl

 

 

 

(Swift 3,4,5...) NTLM Client and Server Code

Demonstrates the NTLM authentication algorithm for both client and server.

Chilkat Downloads for the Swift Programming Language

MAC OS X (Cocoa) Objective-C/Swift Libs

iOS Objective-C/Swift Libs

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

    let ntlmClient = CkoNtlm()!
    let ntlmServer = CkoNtlm()!

    // The NTLM protocol begins by the client sending the server
    // a Type1 message. 
    var type1Msg: String?
    ntlmClient.workstation = "MyWorkstation"
    type1Msg = ntlmClient.genType1()

    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..
    var type1Info: String? = ntlmServer.parseType1(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).
    ntlmServer.targetName = "myAuthRealm"

    var type2Msg: String? = ntlmServer.genType2(type1Msg)
    if ntlmServer.lastMethodSuccess != true {
        print("\(ntlmServer.lastErrorText!)")
        return
    }

    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.
    var type2Info: String? = ntlmClient.parseType2(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:
    ntlmClient.userName = "test123"
    ntlmClient.password = "myPassword"

    var type3Msg: String?
    type3Msg = ntlmClient.genType3(type2Msg)
    if ntlmClient.lastMethodSuccess != true {
        print("\(ntlmClient.lastErrorText!)")
        return
    }

    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.

    var success: Bool = ntlmServer.loadType3(type3Msg)
    if success != true {
        print("\(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.
    var clientUsername: String? = 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:
    var expectedType3Msg: String? = ntlmServer.genType3(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

}

 

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