pkispawn accepts a non-existing ldap instance name during installation
Steps to Reproduce:
1. Create an ldap instance with the name pki-ca (slapd-pki-ca) using port 389 and base dn dc=pki-ca 2. Use the following installation file for CA [DEFAULT] pki_instance_name = pki-ca-foobar-May16 pki_https_port = 20443 pki_http_port = 20080 pki_token_password = <password> pki_admin_password = <password> pki_hostname = pki.example.com pki_security_domain_name = topology-02_Foobarmaster.org pki_security_domain_password = <password> pki_client_dir = /opt/pki-ca-foobar-May16 pki_client_pkcs12_password = pki_ds_password = pki_ds_ldap_port = 389 pki_token_password= [Tomcat] pki_ajp_port = 20009 pki_tomcat_server_port = 20005 [CA] pki_import_admin_cert = False pki_ds_hostname = pki.example.com pki_admin_nickname = PKI CA Administrator for Example.Org 3. pkispawn CA
Actual results:
pkispawn is successful and the database name used by CA is pki-ca-foobar-May16-CA and base dn used is o=pki-ca-foobar-May16-CA
Expected results:
Additional info:
This will lead to issues during db2ldif and ldif2db
Metadata Update from @mharmsen: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Metadata Update from @mharmsen: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1451494
Metadata Update from @mharmsen: - Custom field origin adjusted to QE (was: Community)
Per PKI Bug Council of May 25, 2017, since a workaround exists (specifying the proper information), this bug will be moved to 10.5.
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5 (was: 0.0 NEEDS_TRIAGE)
Metadata Update from @mharmsen: - Custom field lowhangingfruit adjusted to vakwetu: X - Issue priority set to: minor - Issue set to the milestone: FUTURE (was: 10.5)
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/2826
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.