Installation and Upgrade Guides › Web Agent Installation Guide › Install a Web Agent on a UNIX System › Register a Trusted Host in GUI or Console Mode › Re-register a Trusted Host Using the Registration Tool (UNIX)

Re-register a Trusted Host Using the Registration Tool (UNIX)

When you install a Web Agent on a server for the first time, you are prompted to register that server as a trusted host. After the trusted host is registered, you do not have to re-register with subsequent Agent installations. There are some situations where you may need to re-register a trusted host independently of installing an Agent, such as the following:

• To rename the trusted host if there has been a change to your SiteMinder environment.
• To register a trusted host if the trusted host has been deleted in the Policy Server User Interface.
• To register a trusted host if the trusted host policy objects have been deleted from the policy store or the policy store has been lost.
• To change the shared secret that secures the connection between the trusted host and the Policy Server.
• To recreate the SmHost.conf configuration file if it is lost.
• To overwrite an existing trusted host without deleting it first.

The registration tool, smreghost, re-registers a trusted host. This tool is installed in the web_agent_home/bin directory when you install a Web Agent.

Note: The web_agent_home variable indicates the installed location of the Web Agent, as shown in the following examples:

• For Windows installations, the default location is C:\Program Files\netegrity\webagent
• For UNIX installations, the default location is user_home_directory/netegrity/webagent
• For z/OS installations, the default location is /siteminder/v_number_of_version/webagent/

To re-register a trusted host using the registration tool

Open a command prompt window.

1. Ensure that the library path environment variable contains the path to the Web Agent’s bin directory.
2. Enter the following two commands:

   library_path_variable=${library_path_variable}:web_agent_home/bin

   export library_path_variable

   For example, for Solaris systems enter the following two commands:

   LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:/usr/netegrity/webagent/bin

   export LD_LIBRARY_PATH

   The following list shows the different variables for each operating system:

   Solaris

   LD_LIBRARY_PATH

   HP-UX

   SHLIB_PATH

   LINUX

   LD_LIBRARY_PATH

   AIX

   LIBPATH

3. Enter the smreghost command using the following required arguments, as shown in the following example:

   smreghost -i policy_server_IP_address:[port]

   -u administrator_username -p Administrator_password

   -hn hostname_for_registration -hc host_configuration_ object

   Note: There should be a space between each command argument and its value.

   Example:

   smreghost -i 123.123.1.1 -u SiteMinder -p mypw -hn hostA
   -hc DefaultHostSettings

   Example with the -o argument:

   smreghost -i 123.123.1.1 -u SiteMinder -p mypw -hn hostA -hc DefaultHostSettings -o

   The following arguments are used with the smreghost command:

   -i policy_server_IP_ address:port

   Indicates the IP address of the Policy Server where you are registering this host. Specify the port of the authentication server only if you are not using the default port.

   If you specify a port number, which can be a non-default port, that port is used for all three Policy Server servers (authentication, authorization, accounting), however, the unified server responds to any Agent request on any port. For example, if you specify port 55555, the policy server entry in the SmHost.conf file will show the following:

   "policy_server_ip_address,5555,5555,5555"

   Example: 127.0.0.1,44442

   -u administrator_username

   Indicates Name of the SiteMinder administrator with the rights to register a trusted host.

   -p Administrator_password

   Indicates the password of the Administrator who is allowed to register a trusted host.

   -hn hostname_for_registration

   Indicates the name of the host to be registered. This can be any name that identifies the host, but it must be unique. After registration, this name is placed in the Trusted Host list in the Policy Server User Interface.

   -hc host_config_object

   Indicates the name of the Host Configuration Object configured at the Policy Server. This object must exist on the Policy Server before you can register a trusted host.

   -f path_to_host_config_file

   (Optional) Indicates the full path to the file that contains the registration data. The default file is SmHost.conf. If you do not specify a path, the file is installed in the location where you are running the smreghost tool.

   If you use the same name as an existing host configuration file, the tool backups up the original and adds a .bk extension to the backup file name.

   -o

   Overwrites an existing trusted host. If you do not use this argument, you will have to delete the existing trusted host with the Policy Server User Interface before using the smreghost command. We recommend using the smreghost command with this argument.

   The trusted host is re-registered.