PowerShell

Use Installed Cert on Windows for TLS Client Authentication

See more HTTP Examples

Demonstrates how to use a certificate that has already been installed on a Windows PC for TLS client authentication. PowerShell

Add-Type -Path "C:\chilkat\ChilkatDotNet47-x64\ChilkatDotNet47.dll"

$success = $false

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

$http = New-Object Chilkat.Http

# On Windows, a pre-installed certificate can be loaded in a number of different ways.
# This example loads by the common name:
$cert = New-Object Chilkat.Cert
$success = $cert.LoadByCommonName("My ECA Medium Assurance Identity Certificate")
if ($success -ne $true) {
    $($cert.LastErrorText)
    exit
}

# Make sure this certificate has a private key available.  
# It should be a private key such that when the certificate was installed, it was marked as "exportable"
# so that authorized programs are able to access the private key.
if ($cert.HasPrivateKey() -ne $true) {
    $("A private key is needed for TLS client authentication.")
    $("This certificate has no private key.")
    exit
}

# Set the certificate to be used for mutual TLS authentication
# (i.e. sets the client-side certificate for two-way TLS authentication)
$success = $http.SetSslClientCert($cert)
if ($success -ne $true) {
    $($http.LastErrorText)
    exit
}

# At this point, the HTTP object instance is setup with the client-side cert, and any SSL/TLS
# connection will automatically use it if the server demands a client-side cert.