Fwd: [dogtagpki] Issue #3040: pki-ca using existing CA
by Matthew Harmsen
hamzah reported a new issue against the project: `dogtagpki` that you are following:
``
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(a)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=https://api3.ows.bf2.yahoo.com:8373
pki_clone_replicate_schema=True
pki_security_domain_password=
pki_clone_pkcs12_path=/tmp/ca-certs.p12
pki_clone_pkcs12_password=
now am getting the error
because of the change below
https://github.com/dogtagpki/pki/commit/313c701957bedfd59f7f6368d0c37d292...
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 i still get an error
may be because am importing the CA cert twice
``
To reply, visit the link below or just reply to this email
https://pagure.io/dogtagpki/issue/3040
6 years, 4 months
- 1
- 0
- ← Newer
- 1
- Older →