PowerShell
PowerShell
Sign a JWS with an HMAC Key
See more JSON Web Signatures (JWS) Examples
Demonstrates Jws.SetMacKey, which sets the symmetric MAC key for a signature. The key bytes are supplied in a named encoding such as hex or base64.
Background. HMAC-based JWS (for example HS256) authenticates the payload with a shared symmetric key that both signer and verifier possess.
Chilkat PowerShell Downloads
Add-Type -Path "C:\chilkat\ChilkatDotNet47-x64\ChilkatDotNet47.dll"
$success = $false
$jws = New-Object Chilkat.Jws
# Protected header specifying HMAC-SHA256.
$header = New-Object Chilkat.JsonObject
$header.UpdateString("alg","HS256")
$success = $jws.SetProtectedHeader(0,$header)
if ($success -eq $false) {
$($jws.LastErrorText)
exit
}
$bIncludeBom = $false
$success = $jws.SetPayload("This is the content to sign.","utf-8",$bIncludeBom)
if ($success -eq $false) {
$($jws.LastErrorText)
exit
}
# Set the symmetric MAC key for signature 0. The key bytes are provided in the named encoding (here
# base64). In production, obtain the key from a secure source rather than hard-coding it.
$base64Key = "YWJjZGVmZ2hpamtsbW5vcHFyc3R1dnd4eXowMTIzNDU="
$success = $jws.SetMacKey(0,$base64Key,"base64")
if ($success -eq $false) {
$($jws.LastErrorText)
exit
}
$jwsCompact = $jws.CreateJws()
if ($jws.LastMethodSuccess -eq $false) {
$($jws.LastErrorText)
exit
}
$($jwsCompact)