Site-specific authentication uses a site’s secret to authenticate connections. When corresponding records in serverConnect.conf and clientConnect.conf contain the <AUTO> value for both the SDK 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 SDK installations.

So for connections to a particular Domain Manager (such as Service Assurance Manager), you could define a record in serverConnect.conf:

GM-Company-1:<AUTO>:<AUTO>:All

Then define a corresponding record in the clientConnect.conf files on the different hosts connecting to the server:

*:GM-Company-1:<AUTO>:<AUTO>

As long as both the client and server use the same secret phrase, the server will authenticate each connection to the Domain Manager.

Note:

Do not use <AUTO> for the brokerConnect.conf if it is used for other connections, because the Broker does not need All access, only Ping.