SSL inspection causing certificate issues with web developer tools

[nashcoop]

We're running into a problem with SSL inspection causing certificate issues with some of our web developer tools like Ubuntu when it makes calls on port 443.  MWG reporting doesn't seem to recognize these problems, and I'm usually able to workaround it by adding the hostname (after the end user tells me what it is) it's calling out to into the MCP bypass list or whitelisting it on the gateway, however I'd like to know if there's a way to fix the problem on the front end in the web developer tools.  Perhaps importing the certificate into them?  Any help would be appreciated. 

[aloksard · Accepted solution]

Hi,

Hope you are doing well.

When MWG doing SSL inspection , in that case MWG generates a certificate on the fly for the HTTPS website requested, so if the client is not able to trust that certificate then SSL handshake fails and you can see Unknown CA/CERT_AUTHORITY_INVALID kind of errors.  You can take a packet capture or check for any log at client side to confirm on the same.  If yes then importing the certificate into them will help.

When you bypass SSL inspection in that case SSL handshake happens directly between client and destination server and certificate is received from actual destination server which the client side is successfully able to trust.

Regards

Alok Sarda