Generate SHA1 thumbprint of incoming SSL cert

X509::hash will return the md5 hash of the binary cert. sha1 will return the sha1 hash.

 

 

Also, a client can resume an existing SSL session and not present the client cert in a new handshake for every TCP connection or HTTP request. TMM automatically stores the cert for the life of the SSL session and makes it accessible using [SSL::cert 0]. So it's better to get the value on each HTTP request instead of storing it in a local variable which is specific to that one TCP connection.

 

 

Long story short...the last example I posted should work for your scenario.

 

 

Aaron