Technical Blog Post
Abstract
Certificate/protocol troubleshooting in IBM Sterling B2B Integrator: How to capture Certificate using Wireshark.
Body
Author: Manisha Khond, IBM Cognitive Engagement, Watson Supply Chain.
One of the steps in analyzing certificate/protocol issues is capturing the certificates from the network trace.
The captured certificate can be analyzed and used in further testing to troubleshoot an issue.
This blog explains how you can capture the certificates using Wireshark.
| Open the network capture using Wireshark. |
| Make sure the setting "Allow subdissector to reassemble TCP streams" is 'checked' in the TCP protocol preferences. |
 |
| Go to the packet which contains the SSL handshake message "Certificate". |
 |
| In the packet detail pane, expand the Secure Socket Layer. |
 |
| Expand the TLS Record Layer. |
 |
| Expand the Handshake Protocol: Certificate. |
 |
Expand the list of certificates. There is a list of certificate length and certificates (the list could be only 1 certificate). The first certificate is the server certificate, the second it's signing CA, the third the CA that signed the CA, etc. |
 |
| Right click on the certificate that you want to export. |
Choose "Export Selected Packet Bytes...". |
 |
Choose a filename and click on save. After save, you can rename the certificate with .crt extension. |
|
For questions or comments on the blog, please use the feedback section. |
UID
ibm11121169