When a trigger script executes on a client machine, it runs under the identity of the AccuRev user who entered the command. Since the user himself is registered (i.e. has a
principal-name) in the AccuRev user registry, there won’t be any authentication problems if the trigger script runs AccuRev commands that access the repository.
We recommend against using the login command to set the AccuRev username in the script itself. You would have to include the password for the AccuRev username in the script; this presents a significant security risk.