Secure configuration file examples

The following examples serve as sample uses of the fields available in a secure file. To generate entries in a secure file like those shown below, use the secadmin utility. Using the secadmin utility ensures that the secure file is formatted correctly. For more information, see Using the secadmin utility.

• A typical default entry for BMC Server Automation clients:
  default:port=4750:protocol=5:encryption=tls
  
• A subnet in an entry:
  @192.168.12.13/24:protocol=5:encryption=tls
  

• Instructs a Network Shell client to communicate with a Network Shell proxy server using an authentication profile called QAProfile. The authentication profile is stored in the default location for the authentication profile file: 

  
  default:protocol=5:encryption=tls:appserver_protocol=ssoproxy:auth_profile=QAProfile:
  auth_profiles_file=/opt/bmc/bladelogic/NSH/br/authenticationProfiles.xml
  
• Shows how to use a port other than the default port of 4750. If you use host1 as the client host and host2 as the remote host, the following entry should be in the secure file of host1
  host2:port=987
  while the following entry should be in the secure file of host2:
  host1:port=987
  
• Shows how to instruct the RSCD agent to listen on a specific address for client connections:
  rscd:host=192.168.10.20