Bug 467967 - exception in UpdateDomainXML is not caught by pkiremove when an invalid client cert is presented
Summary: exception in UpdateDomainXML is not caught by pkiremove when an invalid clien...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Dogtag Certificate System
Classification: Retired
Component: Installation Wizard
Version: 1.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ade Lee
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-21 22:40 UTC by Ade Lee
Modified: 2020-03-27 18:36 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-27 18:36:35 UTC
Embargoed:


Attachments (Terms of Use)

Description Ade Lee 2008-10-21 22:40:24 UTC
Description of problem:

Problem is actually error handling in updateDomainXML.  When an existing domain is updated, if an invalid client cert is presented, then an exception is thrown.  This exception is not caught and returned as an error to the client, resulting in a silent (unseen) failure to update the domain.

This needs to be fixed.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Ade Lee 2009-01-05 17:01:16 UTC
changes checked in with 472006

Comment 2 Chandrasekar Kannan 2009-06-09 23:25:58 UTC
please provide some steps to verify

Comment 3 Ade Lee 2009-07-02 15:07:34 UTC
This error arose when I was messing around with installations and my system got a little messed up from previous failed installations.  This is a little tough to verify.  You might be able to do this ..

1. Install and configure a CA
2. Install another subsystem (say a KRA) and have it join the CA's domain.  Go through the installation steps and just before clicking to get to the last page - go into the CA console and replace the cert for the KRA agent/admin with another cert.  The cert should be the KRA subsystem cert.

Updating the security domain will fail.  Before the fix, this failure will occur silently.  After this fix, the failure should generate an exception.


Note You need to log in before you can comment on or make changes to this bug.