[Pki-devel] [PATCH] 326 Fixed problem running GroupMemberProcessor on non-CA.

[Endi Sukma Dewata]

On 10/10/2013 10:00 AM, Endi Sukma Dewata wrote:
> Previously the GroupMemberProcessor could only run on CA because the
> base Processor class depends on CA. To fix the problem all CA-specific
> code in Processor has been moved into a new CAProcessor. All existing
> subclasses of Processor will inherit from CAProcessor, but the
> GroupMemberProcessor will continue to inherit from Processor.

Reposted as separated patches. The first one renames Processor to 
CAProcessor to reflect the current CA dependency issue. The second one 
creates a new generic Processor super class to fix GroupMemberProcessor 
issue. Please apply in this order: 331, 326-1.

As Ade noted, there are additional works to be done:
1. Some other non-CA-specific fields/methods should be moved to the 
super class as well including stats, getSSLClientCertificat(), maybe the 
authenticate().
2. SecurityDomainProcessor will need to run on a standalone KRA, so it 
should not inherit from CAProcessor either.

-- 
Endi S. Dewata
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pki-edewata-0331-Renamed-Processor-to-CAProcessor.patch
Type: text/x-patch
Size: 12347 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/pki-devel/attachments/20131028/bf8d4b78/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pki-edewata-0326-1-Fixed-problem-running-GroupMemberProcessor-on-non-CA.patch
Type: text/x-patch
Size: 11569 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/pki-devel/attachments/20131028/bf8d4b78/attachment-0001.bin>