What Do I Do If the Third-Party System Fails to Be Interconnected After the Patch Is Installed
Question
What do I do if the third-party system fails to be interconnected after a patch of eSight V300R010C00SPC630 or a later version or a patch of V300R010C00CP5030 or a later version is installed?
Answer
The cause is that the insecure CBC encryption algorithm is deleted from the patch version. You can perform the following operations to add the corresponding encryption algorithm:
- Log in to the current eSight server as the ossuser user.
In a HA scenario, you need to perform the operations only on the active server.
- Add the configuration item ssl.include.ciphers to the configuration file /opt/eSight/AppBase/etc/oms.ros/ros_config_esight.xml and set its value as follows:
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <webservers> <webserver name="rosOpenAPIROA"> <connectors> <connector name="openapiROAConnector" type="https"> <property name="ip" value="10.243.1.42"/> <property name="ssl.include.ciphers" value="TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA256;TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256;TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA;TLS_RSA_WITH_AES_256_CBC_SHA256;TLS_RSA_WITH_AES_256_CBC_SHA;TLS_RSA_WITH_AES_128_CBC_SHA256;TLS_RSA_WITH_AES_128_CBC_SHA"/> </connector> </connectors> </webserver> <webserver name="rosRoaIntegrateROA"> <property name="roa.server.ip.white.list.enable" value="false"/> <connectors> <connector name="roaIntegrateROAConnector" type="https"> <property name="ip" value="10.243.1.42"/> </connector> </connectors> </webserver> </webservers>
- After the modification, restart eSight for the configuration file to take effect. Interconnect with the third-party system again.