Authenticating site-specific connections

Site-specific authentication involves the use of a site’s secret to authenticate connections.

When corresponding records in serverConnect.conf and clientConnect.conf contain the <AUTO> value for both the Smart Assurance username and password, the client generates a password by using its secret. The server validates the password to accept or reject the connection.

Note: Do not use this method unless you have changed the default site secret. The default site secret is known to all Smart Assurance installations.

Procedure

1. For connections to a particular Domain Manager, for example, Service Assurance Manager, define a record in the serverConnect.conf file.
   GM-Company-1:<AUTO>:<AUTO>:All
2. Define a corresponding record in the clientConnect.conf file on the different hosts connecting to the server:
   *:GM-Company-1:<AUTO>:<AUTO>