Secure mode for gateways

When you start the ObjectServer in secure mode, by using the -secure command-line option, it authenticates probe, gateway, and proxy server connections by requiring a user name and password.

When a connection request is sent, the ObjectServer issues an authentication message. The probe, gateway, or proxy server must respond with the correct user name and password. If the user name and password combination is incorrect, the ObjectServer issues an error message and rejects the connection.

If the ObjectServer is not running in secure mode, probe, gateway, and proxy server connection requests are not authenticated.

Secure authentication is configured differently for gateways that use single configuration files (.conf files) and for gateways that use properties files (.props files). See the individual gateway reference guides for gateway-specific configuration information.

You can use the nco_g_crypt utility to encrypt passwords for use in configuration and properties files. If you are running Tivoli Netcool/OMNIbus in FIPS 140-2 mode, use the nco_aes_crypt utility to encrypt passwords. Encrypted passwords are decoded by the gateway before they are used to log in to the target system. See the individual gateway reference guides for gateway-specific information about encrypting passwords.

For more information about running the ObjectServer and ObjectServer Gateway in secure mode and FIPS 140–2 mode, see the IBM Tivoli Netcool/OMNIbus Installation and Deployment Guide and the IBM Tivoli Netcool/OMNIbus ObjectServer Gateway Reference Guide.