dogtagpki

#3040 pki-ca using existing CA
Closed: fixed Opened by hamzah.

Closed: fixed
Reopen Issue

i have the following CA configuration which used to work with pki-ca 10.5.1 package before the 13 release
[CA]
pki_admin_email=caadmin@example.com
pki_admin_name=caadmin
pki_admin_nickname=caadmin
pki_admin_password=
pki_admin_uid=caadmin
pki_backup_password=
pki_client_database_password=
pki_client_database_purge=False
pki_client_pkcs12_password=
pki_clone_pkcs12_password=
pki_ds_base_dn=dc=ca,dc=example,dc=com
pki_ds_database=ca
pki_ds_password=
pki_security_domain_name=EXAMPLE
pki_token_password=
pki_https_port=8373
pki_http_port=8370
pki_ajp_port=8379
pki_tomcat_server_port=8375

pki_security_domain_hostname=...
pki_security_domain_https_port=8373

pki_clone=True
pki_clone_uri=server
pki_clone_replicate_schema=True
pki_security_domain_password=
pki_clone_pkcs12_path=/tmp/ca-certs.p12
pki_clone_pkcs12_password=

now am getting an error
because of the change below
https://github.com/dogtagpki/pki/commit/313c701957bedfd59f7f6368d0c37d2928d1a4a1

in the file
base/server/python/pki/server/deployment/scriptlets/configuration.py
line 403

since the code just through an exception when this 'pki_ca_signing_cert_path' configuration does not exist, but am using 'pki_clone_pkcs12_path' instead and even if i include it in the configuration i still get another error
may be because am importing the CA cert twice

Metadata Update from @mharmsen:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

Metadata Update from @rpattath:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1633761

Metadata Update from @edewata:
- Issue assigned to edewata

Fixed in master branch:
* https://github.com/dogtagpki/pki/commit/7dbd650c3a2fbebd67e0cc7fc006b0ef50feb61a

Fixed in 10.5 branch:
* https://github.com/dogtagpki/pki/commit/a4f5b17ee96adf79391f9def6e04bb239a779cbe

Metadata Update from @edewata:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

Metadata Update from @edewata:
- Issue set to the milestone: 10.5.13 (was: 0.0 NEEDS_TRIAGE)

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/3158

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.
Metadata
None
None
None
None
None
None
None
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.