|
|
(Tcl) Sign XML (XAdES) in the Cloud using Azure Key Vault
Demonstrates how to sign XML using Azure Key Vault. The signing of the hash happens in the Cloud on Azure Key Vault. Everything else involving the updating the XML to add the signature happens locally within Chilkat.
Note: This example requires Chilkat v9.5.0.96 or greater.
load ./chilkat.dll
# This example requires the Chilkat API to have been previously unlocked.
# See Global Unlock Sample for sample code.
# Create the XML to be signed.
set sbXml [new_CkStringBuilder]
set bCrlf 1
CkStringBuilder_AppendLine $sbXml "<?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"no\" ?>" $bCrlf
CkStringBuilder_AppendLine $sbXml "<SOAP-ENV:Envelope xmlns:SOAP-ENV=\"http://schemas.xmlsoap.org/soap/envelope/\">" $bCrlf
CkStringBuilder_AppendLine $sbXml " <SOAP-ENV:Header>" $bCrlf
CkStringBuilder_AppendLine $sbXml " <wsse:Security xmlns:wsse=\"http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd\" SOAP-ENV:mustUnderstand=\"1\"></wsse:Security>" $bCrlf
CkStringBuilder_AppendLine $sbXml " </SOAP-ENV:Header>" $bCrlf
CkStringBuilder_AppendLine $sbXml " <SOAP-ENV:Body xmlns:SOAP-SEC=\"http://schemas.xmlsoap.org/soap/security/2000-12\" SOAP-SEC:id=\"Body\">" $bCrlf
CkStringBuilder_AppendLine $sbXml " <z:FooBar xmlns:z=\"http://example.com\" />" $bCrlf
CkStringBuilder_AppendLine $sbXml " </SOAP-ENV:Body>" $bCrlf
CkStringBuilder_AppendLine $sbXml "</SOAP-ENV:Envelope>" $bCrlf
# Load the certificate used for signing. The certificate's private key is stored in
# the Azure Key Vault.
# However, we still need the certificate locally (without private key).
set cert [new_CkCert]
set success [CkCert_LoadFromFile $cert "qa_data/certs/myCert.cer"]
if {$success == 0} then {
puts [CkCert_lastErrorText $cert]
delete_CkStringBuilder $sbXml
delete_CkCert $cert
exit
}
# Here's a screenshot of our certificate with private key on Azure Key Vault:
# To sign using the Azure Key Vault,
# add the following lines of code to specify your authentication credentials,
# and the name of the certificate w/ private key on the Azure server to be used.
set jsonAzure [new_CkJsonObject]
# Set the "service" equal to "azure_keyvault" to tell Chilkat to use Azure Key Vault for signing.
CkJsonObject_UpdateString $jsonAzure "service" "azure_keyvault"
CkJsonObject_UpdateString $jsonAzure "client_id" "APP_ID"
CkJsonObject_UpdateString $jsonAzure "client_secret" "APP_PASSWORD"
CkJsonObject_UpdateString $jsonAzure "tenant_id" "TENANT_ID"
# In the above screenshot, our vault name is "kvchilkat". You will use your vault name.
CkJsonObject_UpdateString $jsonAzure "vault_name" "VAULT_NAME"
# In the above screenshot, our cert name is "ChilkatTest1". You will use your cert name.
CkJsonObject_UpdateString $jsonAzure "cert_name" "CERT_NAME"
# In the above screenshot, our cert version is "63b94a23389546ecbc8eb6208a1bef37". You will use your cert version.
CkJsonObject_UpdateString $jsonAzure "cert_version" "CERT_VERSION"
set success [CkCert_SetCloudSigner $cert $jsonAzure]
# Prepare for signing...
set gen [new_CkXmlDSigGen]
# Indicate where the Signature will be inserted.
CkXmlDSigGen_put_SigLocation $gen "SOAP-ENV:Envelope|SOAP-ENV:Header|wsse:Security"
# Add a reference to the fragment of the XML to be signed.
# Note: "Body" refers to the XML element having an "id" equal to "Body", where "id" is case insensitive
# and where any namespace might qualify the attribute. In this case, the SOAP-ENV:Body fragment is signed
# NOT because the tag = "Body", but because it has SOAP-SEC:id="Body"
CkXmlDSigGen_AddSameDocRef $gen "Body" "sha1" "EXCL_C14N" "" ""
# (You can read about the SignedInfoPrefixList in the online reference documentation. It's optional..)
CkXmlDSigGen_put_SignedInfoPrefixList $gen "wsse SOAP-ENV"
CkXmlDSigGen_put_KeyInfoType $gen "X509Data"
CkXmlDSigGen_put_X509Type $gen "IssuerSerial"
set bUsePrivateKey 1
set success [CkXmlDSigGen_SetX509Cert $gen $cert $bUsePrivateKey]
if {$success != 1} then {
puts [CkXmlDSigGen_lastErrorText $gen]
delete_CkCert $cert
delete_CkStringBuilder $sbXml
delete_CkCert $cert
delete_CkJsonObject $jsonAzure
delete_CkXmlDSigGen $gen
exit
}
# Everything's specified. Now create and insert the Signature
# (The actual signing of the hash will happen on the Aruba server.)
set success [CkXmlDSigGen_CreateXmlDSigSb $gen $sbXml]
if {$success != 1} then {
puts [CkXmlDSigGen_lastErrorText $gen]
delete_CkStringBuilder $sbXml
delete_CkCert $cert
delete_CkJsonObject $jsonAzure
delete_CkXmlDSigGen $gen
exit
}
# Examine the XML with the digital signature inserted
puts [CkStringBuilder_getAsString $sbXml]
# --------------------------------------------------------------------------------
# Also see Chilkat's Online WSDL Code Generator
# to generate code and SOAP Request and Response XML for each operation in a WSDL.
# --------------------------------------------------------------------------------
delete_CkStringBuilder $sbXml
delete_CkCert $cert
delete_CkJsonObject $jsonAzure
delete_CkXmlDSigGen $gen
|
