![report server configuration file secure file connection i report server configuration file secure file connection i](https://user-images.githubusercontent.com/26415925/95482647-0c89c800-0997-11eb-83c0-4516c6cdb42e.png)
Using the secadmin utility ensures that the secure file is formatted correctly.
#Report server configuration file secure file connection i full
See Security planning for a full description of all the procedures needed to implement security in a TrueSight Server Automation system.Īlways use the secadmin utility to modify the secure file. Stronger security requires additional modifications to a system. The port number can be set with an entry in the Internet services databases (for example, /etc/services ).įor simpler security installations, you need only modify the secure file to establish how data is communicated between clients and servers. The exports, users, and users.local files control user access to servers (see Configuring the exports file and Configuring the users or users.local files).īy default, client and server processes communicate using TCP/IP port 4750 with the server process listening on all configured NIC (Network Interface Card) addresses. The secure file on the server defines parameters that the RSCD agent uses to communicate with TrueSight Server Automation applications on clients. The secure file for a client application defines parameters that TrueSight Server Automation applications use to communicate with the RSCD agent on a server. In this discussion, a client application can be a Network Shell client, TrueSight Server Automation Application Server, or Network Shell proxy server that communicates directly with an RSCD agent or repeater. The secure file defines how TrueSight Server Automation applications for a client installation and the RSCD agent on a server communicate with each other. Configuring the users or users.local filesĬonfiguring the securecert file About the secure file