Table 8-8 describes the configuration parameters generally available for all pathways. Exceptions and special cases are listed in Table 8-7 and described in detail in each pathway section.
configuration_parameter |
Description |
|---|---|
msg_confidentiality |
Indicates whether Replication Server sends and receives encrypted data. If set to “required,” outgoing and incoming data must be encrypted. If set to “not_required,” Replication Server accepts incoming data that is encrypted or not encrypted. Values are “required” or “not_required.” Default: not_required |
msg_integrity |
Indicates whether data is checked for tampering. Values are “required” or “not_required.” Default: not_required |
msg_origin_check |
Indicates whether the source of data must be verified.Values are “required” or “not_required.” Default: not_required |
msg_replay_detection |
Indicates whether data should be checked to make sure it has not been intercepted and re-sent.Values are “required” or “not_required.” Default: not_required |
msg_sequence_check |
Indicates whether data packages should be checked to ensure that they have been received in the order sent. Values are “required” or “not_required.” Default: not_required |
mutual_auth |
Requires remote server to provide proof of identify before a connection can be established. Values are “required” or “not_required.” Default: not_required |
security_mechanism |
Specifies the name of the network-based security mechanism. Default: First security mechanism listed in libtcl.cfg. |
unified_login |
Indicates how Replication Server seeks outgoing connections and accepts incoming connections. The values are:
Default: not_required |
unified_login must be “required” before
other security parameters can take effect.