PowerShell

Use HTTPS Client Certificate from .cer and .key Files

See more HTTP Examples

Demonstrates how to load a cert + private key from .cer and .key (base64) files and use it for mutual TLS authentication (client-side certificate). 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

$cert = New-Object Chilkat.Cert
$privKey = New-Object Chilkat.PrivateKey

# Load any type of certificate (.cer, .p7b, .pem, etc.) by calling LoadFromFile.
$success = $cert.LoadFromFile("qa_data/certs/sample_cert_a.cer")
if ($success -ne $true) {
    $($cert.LastErrorText)
    exit
}

# Load the private key.
$bd = New-Object Chilkat.BinData
$success = $bd.LoadFile("qa_data/certs/sample_key_a.key")
$success = $privKey.LoadAnyFormat($bd,"privateKeyPasswordIfNecessary")
if ($success -ne $true) {
    $($privKey.LastErrorText)
    exit
}

# Associate the private key with the cert.
$success = $cert.SetPrivateKey($privKey)
if ($success -ne $true) {
    $($cert.LastErrorText)
    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.