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
(PowerBuilder) HTTP TLS Mutual Authentication (Client-Side Certificate)This example demonstrates what to do when a TLS connection requires a client-side certificate, also known as "two-way authentication" or "mutual authentication". The Chilkat API provides a few standard methods for setting the client-side certificate:
These methods are present in any Chilkat class that has SSL/TLS functionality. When the SSL client cert is set via one of these methods, it tells the API to use it for two-way (i.e. mutual) authentication. In all possible tasks, whether it is a POST, GET, PUT, an Amazon S3 method, etc., the only thing required for implementing the two-way authentication is to make a successful call to one of the above SetSsl* methods.
integer li_rc oleobject loo_Http integer li_Success // This example assumes the Chilkat API to have been previously unlocked. // See Global Unlock Sample for sample code. loo_Http = create oleobject // Use "Chilkat_9_5_0.Http" for versions of Chilkat < 10.0.0 li_rc = loo_Http.ConnectToNewObject("Chilkat.Http") if li_rc < 0 then destroy loo_Http MessageBox("Error","Connecting to COM object failed") return end if // Set the certificate to be used for mutual TLS authentication // (i.e. sets the client-side certificate for two-way TLS authentication) li_Success = loo_Http.SetSslClientCertPfx("/home/bob/pfxFiles/myClientSideCertWithPrivateKey.pfx","pfxPassword") if li_Success <> 1 then Write-Debug loo_Http.LastErrorText destroy loo_Http return end if // Note: The certificate used for the client-side of TLS mutual authentication // must have the associated private key available. (PFX files typically store both // the certificate and associated private key.) // At this point, the HTTP object is setup with the client-side cert, and any SSL/TLS // connection will automatically use it if the server demands a client-side cert destroy loo_Http |
© 2000-2024 Chilkat Software, Inc. All Rights Reserved.