Manage Replication Server System Security

You must establish login names and passwords for the various components of the Replication Server system, including RSSDs, RepAgent, the ID Server, and Replication Server.

Often, one process must log in to another, remote process. In such cases, the login name and password assigned to the process logging in must also exist at the remote process. If a password used to log in to the remote process is changed at the current process only, login attempts fail.

As a general rule, if you are specifying or modifying system login names, keep the names unique. If you use the same login name for different roles, then any time you change the password, many of the dependencies described in this section are affected.

• Replication System Login Names
  There are several login names required for replication system components.
• RSSD Login Names and Passwords
  Replication Server uses the primary user and maintenance user login names to manage security.
• Replication Server Login Name and Password for RepAgent
  Learn the guidelines, commands, and procedures to change the Replication Server login name and password for RepAgent.
• ID Server Login Name and Password
  Learn the guidelines to change the ID Server login name and password.
• Replication Server Login Name and Password for Replication Servers
  Replication Servers log in to other Replication Servers to send operations.
• Maintenance User Adaptive Server Login Name and Password
  Replication Servers log in to Adaptive Server for the RSSD database or a user database using the maintenance user login name. When applying insert, delete, or update primary operations to replicate databases, Replication Server uses the maintenance user login name and password.
• Maintenance User Security
  To increase security, prevent unauthorized access to the database, and restrict maintenance user access to Replication Server, secure the maintenance user with password encryption, and set an expiration interval for the password.
• Password Encryption
  Replication Server encrypts all passwords, and stores and transmits passwords in encrypted format.
• Send Encrypted Passwords for Replication Server Client Connections
  Replication Server supports the -X option in isql that sends encrypted passwords through the network when making a client connection
• Existing Encrypted Password Migration
  Newly created passwords use the Federal Information Processing Standards (FIPS)-certified 140-2 encryption algorithm.
• Extended Password Encryption Support
  With version 15.1 and later, Replication Server uses Sybase Common Security Infrastructure (CSI) to provide server or client authentication, provide key-pair generation to support extended password encryption, and provide cryptography for encryption and decryption of passwords that are transmitted in the network between Replication Servers, and between Replication Server and the primary and replicate data servers.
• Sybase Central Dependencies
  The Replication Manager logs into the Replication Server and the RSSD using the login names and passwords that you specified when you added the server to Replication Manager.
• Replication Server Object Creation Dependencies
  Login name and password dependencies also apply when you create Replication Server objects, specifically subscriptions and replicated functions (applied and request functions) that are executed at primary or replicate Replication Servers.