Authenticating users

Each must have a ticket for each server the user accesses. The best way to handle this requirement is to set up a single login to the central server The one server that is innermost in a multi-server deployment. In the server specification form field for Services, the central server might be specified as “standard” or “commit-server”. If edge servers are part of the multi-server deployment, the central server must be a commit server. See also 'upstream server'. that is valid across all replica servers. This is particularly useful with failover configurations, when you would otherwise have to re-login to the new target server The immediately upstream server for replica servers, edge servers, standby servers, proxies and brokers. See also 'upstream server' and 'central 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.
  The "any" config is explained in "Viewing the values of configuration variables on all servers" in p4 configure in the P4 CLI Reference.
• 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.

Users will not be able to log into the server if the central server is unavailable.