ACK

Code review of this produced two new TRAC Tickets:
These changes were tested using two scenarios as described in TRAC Ticket #503 - Dogtag 10: Security Domain Issues.

-- Matt

On 02/04/13 17:39, Matthew Harmsen wrote:
On 02/01/13 11:54, Ade Lee wrote:
We want to use the admin interface for installation work.  This patch
moves the interfaces used in cloning from either the EE or agent
interface to the admin one.  See:
http://pki.fedoraproject.org/wiki/8.1_installer_work_for_cloning

Specifically, 
1. Change call to use /ca/admin/ca/getCertChain
2. Remove unneeded getTokenInfo servlet.  The logic not to use this
servlet has already been committed to dogtag 10.
3. Move updateNumberRange to the admin interface.  For backward
compatibility with old instances, the install code will
call /ca/agent/updateNumberRange as a fallback.
4. Add updateDomainXML to admin interface.  For backward compatibility,
updateDomainXML will continue to be exposed on the agent interface with
agent client auth.
5. Changed pkidestroy to get an install token and use the admin
interface to update the security domain.  For backward compatibility,
the user and password and not specified as mandatory arguments -
although we want to do that in future.

Please review, 
Ade
  


_______________________________________________
Pki-devel mailing list
Pki-devel@redhat.com
https://www.redhat.com/mailman/listinfo/pki-devel
Alee,

Sorry, but I require some additional information to properly test this patch for a CA and its clone using a single machine.  Hopefully, I can address these issues relatively quickly tomorrow after obtaining your answers.

I have pulled a new tree after the meeting this morning (which does not include the patches added at 3:49 P. M. by edewata), created a branch, applied all five of your changes, and built and installed the packages on a fresh x86_64 Fedora 18 system (e. g. - 'foobar.example.com').

In order to test the code, I would like to perform the following two tests using a single machine:
  1. pkispawn using the new configuration servlet for both the CA and the CA Clone
  2. pkispawn using the old GUI configuration (by specifying a DEFAULT value of pki_skip_configuration=True) for both CA and the CA Clone
However, with the new interpolation model, I do not know every single value that needs to be overridden to have both the CA and CA Clone, as well as the two directory servers, on the same system.

I have the following:
Questions:
Thanks in advance,
-- Matt


_______________________________________________
Pki-devel mailing list
Pki-devel@redhat.com
https://www.redhat.com/mailman/listinfo/pki-devel