August 2012 - Pki-devel - Dogtag Pki List Archives

Re: [Pki-devel] [PATCH] 28 Ticket 149 - Enhancement - Dogtag 10 - Implementation of search/list functionalities.

by Endi Sukma Dewata

On 8/10/2012 3:10 PM, Abhishek Koneru wrote: > Patch rebased over 27-4. > Please review and commit. ACK. Pushed to master. -- Endi S. Dewata

11 years, 8 months

1
0
0 / 0

Proposed solution for the "pkideployment.cfg" template file . . .

by Matthew Harmsen

Everyone, It has been brought to my attention (and rightly so) that the 'pkideployment.cfg' file required by the 'pkispawn' executable is confusing to use. One suggestion was simply to rename the file from 'pkideployment.cfg' to something like 'pkideployment.cfg.template' to denote that this is actually a template, and not an actual final configuration file, and rely solely upon a well-written man page (see TRAC Ticket #227 - Dogtag 10: Document 'pkideployment.cfg <https://fedorahosted.org/pki/ticket/227>') which is not slated to be finished until the final phase of the Dogtag 10 release. Not everyone likes this suggestion. Another suggestion was to create separate template files for all the various "flavors"/"configurations", but I am not in favor of this approach as it leads to a problem of keeping too much identical information in sync across the various template files. A slight alternative to this would be to create separate sectional files that are pasted together to create a single configuration file (which in my opinion is way too complicated for what should be a relatively simple configuration file). Therefore, I would like to suggest another alternative -- rather than creating one or more "static" templates, I would like to suggest the creation of a simple python script which generates a configuration file suitable for the user's subsystem choice. For example, this simple script could be used to generate a suitable configuration file which could easily be edited by an end-user to produce a 'pkideployment.cfg' configuration file to any one of the following: * CA * KRA * OCSP * TKS * RA * TPS * CA Clone * KRA Clone * OCSP Clone * TKS Clone * External CA (stage 1) * External CA (stage 2) * Subordinate CA 'TRAC Ticket #227 - Dogtag 10: Document 'pkideployment.cfg <https://fedorahosted.org/pki/ticket/227>' will still be utilized to provide details on what all of the various name/value pairs are used for (along with both their resident default values as well as the computed default values of keys which are purposefully left unassigned), as well as provide detailed examples. Please fill free to comment in response to this email and suggest any other alternatives. If the alternative that I suggest here is approved of, I am willing to writeup a brief design document for such a 'pkispawn pkideployment.cfg' configuration file generator. -- Matt

11 years, 8 months

1
0
0 / 0

[PATCH] patch to allow installation of ocsp and tks using pkispawn.

by Ade Lee

Just needed to add a couple of missing files, and reset the resteasy prefix. Will applied on top of Matt's last patch, will allow OCSP and TKS to install. Pushed to master.

11 years, 8 months

1
0
0 / 0

[PATCH] 28 Ticket 149 - Enhancement - Dogtag 10 - Implementation of search/list functionalities.

by Abhishek Koneru

Please review the patch with implementation for Ticket 149 for DogTag 10. The search filter creation is already present. Changed the ds calling function and added pagination. --Abhishek Koneru

11 years, 8 months

2
1
0 / 0

adding subsequent OCSPs

by Andrew Wnuk

This patch corrects process of attaching OCSP subsystem to CA. It improves handling of adding subsequent OCSP subsystems to CA. Bugs: 804179 and 804176.

11 years, 8 months

2
1
0 / 0

'pki-tps-9.0.7-4.fc18' built and released

by Matthew Harmsen

Nathan and Ade, I have performed the following release engineering tasks for Nathan's API patch change for httpd 2.2 --> httpd 2.4: * Dogtag 10 ('master') o 'git am' and 'git push' to 'master' branch * Dogtag 9 ('DOGTAG_9_BRANCH') o 'git add' and 'git commit' of 'pki/patches/0001-Port-TPS-to-httpd-2.4.patch' and 'pki/specs/pki-tps.spec' o 'git commit' and 'git push' to 'DOGTAG_9_BRANCH' branch o published 'http://pki.fedoraproject.org/pki/sources/pki-tps/0001-Port-TPS-to-httpd-2...' o performed successful Koji build of 'pki-tps-9.0.7-4.fc18' + http://koji.fedoraproject.org/koji/buildinfo?buildID=346590 Note that no "Bodhi" tasks are necessary as the only build requested was for Fedora 18 (Rawhide). -- Matt

11 years, 8 months

2
1
0 / 0

[PATCH] 27 Dogtag 10 Beta - Ticket 150 . Implement Cert search/list request in CLI

by Abhishek Koneru

Please review the attached patch, which has the fix for Ticket 150. Implementing interface for all the UI search - request functionality in CLI. Also attached the sample cert request xml form file. --Abhishek Koneru

11 years, 8 months

2
3
0 / 0

[PATCH] 45 - Change selinux context for legacy instances

by Ade Lee

In the new selinux policy, pki_ca_t etc. are all replaced by pki_tomcat_t. To allow old instances to work under dogtag 10, the context in the run scripts needs to change. Also added a rule needed by selinux policy.

11 years, 8 months

1
1
0 / 0

[PATCH] 44 - Fixed operations to operate on correct number of instances

by Ade Lee

Reverted previous fix to pkidaemon and operations. Now, as expected, systemctl start/stop pki-tomcatd(a)foo.service will stop instance foo, whereas pki-tomcatd.target will affect all tomcatd instances. Please review. Ade

11 years, 8 months

1
1
0 / 0

certificate import for IE

by Andrew Wnuk

This patch corrects certificate import for IE Bug: 845387.

11 years, 8 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

Pki-devel August 2012