Each instance needs access to a Fedora Directory Server instance to store requests and records. Each PKI instance may create its own associated internal database, or may share an existing internal database. To share an existing internal database instance, a PKI instance would only need to establish a unique distinguished name (DN) using the field entitled Base DN and a unique database name using the field entitled Database. #if ($clone == "clone")

Replication agreements between the master and clone database instances may be customized. If no master and replication ports are provided, then replication will occur on the same ports used by the Certificate Sever instances to communicate with the directory server. If these ports are LDAPS ports, then the replication traffic will be SSL encrypted. It is still possible to require the replication traffic to be SSL encrypted on the non-SSL port by selecting TLS for Replication Security. In order for this operation to be successful though, the database instances must be SSL enabled before continuing beyond this panel. #end

Note: If the Fedora Directory Server is at a remote host, it is highly recommended that SSL should be used.
#if ($errorString != "")

$errorString #end
#if ($clone == "clone") #else #end

Host:
Port:	SSL
Base DN:
Database:
Bind DN:
Bind Password:

Remove the existing data from the Base DN shown above.

#if ($clone == "clone") #set ($check_none="") #set ($check_tls="") #set ($check_ssl="") #if ($replicationSecurity == "TLS") #set ($check_tls="CHECKED") #elseif ($replicationSecurity == "SSL") #set ($check_ssl="CHECKED") #else #set ($check_none="CHECKED") #end

#end

Replication Details
Master Replication Port:
Clone Replication Port:
Replication Security:	None TLS SSL