[PATCH] 111 - pkidestory does not remove KRA connector
This patch is bigger than I originally planned, but its mostly pretty straightforward. Resolved Trac Ticket 367 - pkidestroy does not remove connector * Added RESTful servlet to add/remove a KRA connector from the CA. * Modified ACL to allow KRA subsystem user to remove connector. * Modified connector code to allow the connector to be replaced without a server restart. * Added functionality to pki CLI to add/remove connector * Added code to pkidestroy to remove the connector (using both pki CLI and sslget) When the issues with pki connection are resolved, we will use that method instead. * Modified sslget to accept HTTP return codes < 300. In this case, we were returning 204 - which is perfectly legitimate. Test this by: 1. Install a CA, KRA 2. pkidestroy the KRA. The KRA connector config should be removed from the CA. 3. Test removing/ adding KRA connector using pki. Thanks, Ade
New patch based on feedback from Endi. This one throws the exceptions from the processor directly. Ade On Thu, 2013-01-10 at 23:01 -0500, Ade Lee wrote:
This patch is bigger than I originally planned, but its mostly pretty straightforward.
Resolved Trac Ticket 367 - pkidestroy does not remove connector
* Added RESTful servlet to add/remove a KRA connector from the CA. * Modified ACL to allow KRA subsystem user to remove connector. * Modified connector code to allow the connector to be replaced without a server restart. * Added functionality to pki CLI to add/remove connector * Added code to pkidestroy to remove the connector (using both pki CLI and sslget) When the issues with pki connection are resolved, we will use that method instead. * Modified sslget to accept HTTP return codes < 300. In this case, we were returning 204 - which is perfectly legitimate.
Test this by: 1. Install a CA, KRA 2. pkidestroy the KRA. The KRA connector config should be removed from the CA. 3. Test removing/ adding KRA connector using pki.
Thanks, Ade _______________________________________________ Pki-devel mailing list Pki-devel@redhat.com https://www.redhat.com/mailman/listinfo/pki-devel
Patch further modified based on feedback from Endi. 1. Fixed the parsing of host:port list in KRAConnectorProcessor code. 2. Changed Resender to use ExecutorService. We need to modify the order in which the Resender hread starts up, so that it occurs after the server is up and accepting connections - just in case the KRA and CA are in the same instance. Please review. Ade On Fri, 2013-01-11 at 10:52 -0500, Ade Lee wrote:
New patch based on feedback from Endi. This one throws the exceptions from the processor directly.
Ade On Thu, 2013-01-10 at 23:01 -0500, Ade Lee wrote:
This patch is bigger than I originally planned, but its mostly pretty straightforward.
Resolved Trac Ticket 367 - pkidestroy does not remove connector
* Added RESTful servlet to add/remove a KRA connector from the CA. * Modified ACL to allow KRA subsystem user to remove connector. * Modified connector code to allow the connector to be replaced without a server restart. * Added functionality to pki CLI to add/remove connector * Added code to pkidestroy to remove the connector (using both pki CLI and sslget) When the issues with pki connection are resolved, we will use that method instead. * Modified sslget to accept HTTP return codes < 300. In this case, we were returning 204 - which is perfectly legitimate.
Test this by: 1. Install a CA, KRA 2. pkidestroy the KRA. The KRA connector config should be removed from the CA. 3. Test removing/ adding KRA connector using pki.
Thanks, Ade _______________________________________________ Pki-devel mailing list Pki-devel@redhat.com https://www.redhat.com/mailman/listinfo/pki-devel
_______________________________________________ Pki-devel mailing list Pki-devel@redhat.com https://www.redhat.com/mailman/listinfo/pki-devel
participants (1)
-
Ade Lee