[EMAIL PROTECTED] wrote:
The REP_dmz was built on the alpha (main) machine. The parameters of setting up the REP_dmz in "Server admin" screen of the PKI residing on the alpha machine are no doubt correct : "Add repository entity" points to the dmz machine.
No, there is a problem here, you need to connect to your DMZ (client) machine, using the Server GUI.
You create the the Repository object called "REP_dmz".
Now, you connect yourself to the PKI GUI on the alpha (main) machine, you import the signature request from "REP_dmz" into the PKI.
You go back to your server GUI, and you import the signature response.
I did not create a separate PKI instance on the (client) dmz machine. In the absence of better advice I assumed both machines would exchange the PKI objects by themselves as a matter of concept.
You must no create another PKI entity.
The entity REP_dmz was definitely not duplicated via synchronizing on the dmz machine. That can be seen from looking into mysql, from the log (attached) and from /var/log/newpki. The REP_dmz was just built on the alpha machine.
I think the problem, comes from your confusion about what the "Address" and "Port" fields are used for, when creating a Repository entity.
Those fields are only used, to tell the PKI entity where this Repository can be accessed, this allows the other entities to know where they should connect to, to have access to their datas.
In no case, a first server will connect to a second one, to tell this second one, "Please create this Repository". The Server Admin, must physically connect to the second server, create the Repository, then it must be declared into the PKI Entity, as mentioned above.
Regards, -- Fr�d�ric Giudicelli http://www.newpki.org _____________________________________________________________________ NewPKI http://www.newpki.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
