Get Certificate As XML (and gets Signature Algorithm Identifier)
Demonstrates how to convert a certificate to XML such that the contents can easily be identified and accessed. Typically, the Chilkat Cert API provides properties and methods to access the most commonly needed pieces of information from a certificate. If a bit of information is not readily available then it can likely be retrieved from the XML representation. One such case is the certificate's signature algorithm identifier.The basic internal format of a certificate is as follows (from section 4.1 of RFC 5280).
Certificate ::= SEQUENCE {
tbsCertificate TBSCertificate,
signatureAlgorithm AlgorithmIdentifier,
signatureValue BIT STRING }
TBSCertificate ::= SEQUENCE {
version [0] EXPLICIT Version DEFAULT v1,
serialNumber CertificateSerialNumber,
signature AlgorithmIdentifier,
issuer Name,
validity Validity,
subject Name,
subjectPublicKeyInfo SubjectPublicKeyInfo,
issuerUniqueID [1] IMPLICIT UniqueIdentifier OPTIONAL,
subjectUniqueID [2] IMPLICIT UniqueIdentifier OPTIONAL,
-- If present, version MUST be v2 or v3
extensions [3] EXPLICIT Extensions OPTIONAL
-- If present, version MUST be v3
}
Chilkat does not expect you to fully understand this notation and structure, but you can see that at a high level, the certificate is a sequence of three things, one after the other (a TBSCertifciate, an AlgorithmIdentifier, and a BIT STRING that is the signature). In XML format, it will look like this:
<sequence>
<sequence>
TBSCertificate goes here...
</sequence>
<sequence>
<oid>1.2.840.113549.1.1.11</oid>
<null />
</sequence>
<bits n="2048">3D20E895... 8DA307EC</bits>
</sequence>
The "oid" specifies the signature algorithm (such as sha256RSA), but it is an OID. In this case, the OID "1.2.840.113549.1.1.11" indicates "sha256WithRSAEncryption". (Google "1.2.840.113549.1.1.11" and you will find the 1st search result is http://www.alvestrand.no/objectid/1.2.840.113549.1.1.11.html. You can lookup any OID this way, to see what it means.)
Chilkat PowerBuilder Downloads
integer li_rc
integer li_Success
oleobject loo_Socket
integer li_UseTls
integer li_MaxWaitMillisec
string ls_TlsServerHost
oleobject loo_Cert
string ls_CertXml
oleobject loo_Xml
oleobject loo_AlgId
string ls_Oid
li_Success = 0
// This example assumes the Chilkat API to have been previously unlocked.
// See Global Unlock Sample for sample code.
loo_Socket = create oleobject
li_rc = loo_Socket.ConnectToNewObject("Chilkat.Socket")
if li_rc < 0 then
destroy loo_Socket
MessageBox("Error","Connecting to COM object failed")
return
end if
li_UseTls = 1
li_MaxWaitMillisec = 20000
ls_TlsServerHost = "www.google.com"
li_Success = loo_Socket.Connect(ls_TlsServerHost,443,li_UseTls,li_MaxWaitMillisec)
if li_Success = 0 then
Write-Debug loo_Socket.LastErrorText
destroy loo_Socket
return
end if
loo_Cert = create oleobject
li_rc = loo_Cert.ConnectToNewObject("Chilkat.Cert")
li_Success = loo_Socket.GetServerCert(loo_Cert)
if li_Success = 0 then
Write-Debug loo_Socket.LastErrorText
destroy loo_Socket
destroy loo_Cert
return
end if
// Close the connection with the server
// Wait a max of 20 millsec for a clean TLS shutdown.
loo_Socket.Close(20)
// Examine the server cert in XML format
ls_CertXml = loo_Cert.ExportCertXml()
Write-Debug ls_CertXml
// Let's parse the XML to get the signature algorithm identifier.
loo_Xml = create oleobject
li_rc = loo_Xml.ConnectToNewObject("Chilkat.Xml")
loo_Xml.LoadXml(ls_CertXml)
// The 2nd child is at index 1.
loo_AlgId = loo_Xml.GetChild(1)
ls_Oid = loo_AlgId.GetChildContent("oid")
Write-Debug "Signature Algorithm OID = " + ls_Oid
destroy loo_AlgId
destroy loo_Socket
destroy loo_Cert
destroy loo_Xml