#2755 pki client-init initializing the directory after the providing wrong host and port
Closed: migrated 3 years ago by dmoluguw. Opened 6 years ago by mharmsen.

pki client-init initiating the client directory after the providing the wrong host and port.

Steps to Reproduce:

[root@pki1 ~]# pki -d nssdb -c FooBar123 -h pk1.asdfexample.com -p 298945080 client-init 
------------------
Client initialized
------------------

Actual results:

Client Directory initialized.

Expected results:

It should throw the error.

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 rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1464147
- Custom field type adjusted to defect
- Custom field version adjusted to ''
- Issue priority set to: critical
- Issue set to the milestone: 10.4

6 years ago

The pki client-init command does not actually make a network connection, so invalid hostname/port will not be validated.

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (was: 10.4)

6 years ago

Metadata Update from @mharmsen:
- Custom field lowhangingfruit adjusted to vakwetu: X
- Issue priority set to: minor (was: critical)
- Issue set to the milestone: FUTURE (was: 10.5)

6 years ago

Per 10.5.x/10.6 Triage: FUTURE

edewata: negative case

Metadata Update from @mharmsen:
- Custom field rhbz reset (from https://bugzilla.redhat.com/show_bug.cgi?id=1464147)

5 years ago

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/2875

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 Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata