Authenticating users

Users must have a ticket for each server they access. The best way to handle this requirement is to set up a single login to the master server, which is valid across all replica servers. This is particularly useful with failover configurations, when you would otherwise have to re-login to the new master server.

You can set up single-sign-on authentication by using two configurables:

• Set auth.id to a unique value for the "any" config, so it is global. This value will replace the IP address in users P4TICKETS files.
• Set rpl.forward.login (set to 1) for the "any" config, so it is inherited by all replicas.

There might be a slight lag while you wait for each replica server to replicate the db.user record from the target server.