Execute the following command with the path found in the prior step. If multiple JRE's are found, use the latest. Find the keytool binary contained in the JRE in The Lab plugins folder. Below the file is referenced as new_root_ca.ser. The IT department maintaining the TLS Interception setup should be able to provide it, and it may also be found pre-installed in the system. Retrieve the root CA certificate used by the TLS Interception setup. Linux: (similarly adapted steps can also be done Windows and OSX, as alternative) Note: Adding this certificate breaks the networking support when run outside of the Enterprise TLS network. Add the following two properties on separate lines at the end of the file: With Finder, use the "Show Package Contents" context menu on "The Lab.app" folder to see the Contents subfolder which is hidden otherwise. The file is located in 'The Lab 2.0.app/Contents/Eclipse'. Windows: The Lab uses the system root CA certificates and hence works if the certificates used are installed in Windows. The CA root certificate used by the TLS Interception setup needs to be added to the list of CA root certificates known to The Lab. On OSX and Linux, The Lab uses built in CA root certificates, hence network connections fail until the setup is adapted. On Windows The Lab uses root CA certificates of the operating system, and hence works if the certificates are installed in the OS. Instead, the traffic received in The Lab gets re-encrypted with security certificates specific to the Enterprise. The reason is that TLS cannot be transparently intercepted. Some Enterprise networks are setup to inspect all the TLS traffic which breaks The Lab's network connections. The Lab uses TLS (Transport Layer Security) network connections to connect to multiple cloud services:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |