#1047 Issues with finding certs with Netscape Extensions using pki cer-find
Closed: wontfix by cipherboy. Opened by mrniranjan.

  1. On a default dogtag 10 installation where there is no profiles which adds Netscape Extensions to certs, pki cert-find with Netscape Cert Extensions options doesn't produce consistent results

The below commands are Entered when there no certs with any Netscape Extensions:

pki cert-find --certTypeSecureEmail off
---------------
0 entries found
---------------
pki cert-find --certTypeSecureEmail on
---------------
0 entries found
---------------
pki cert-find --certTypeSSLClient off
-----------------------------
Number of entries returned 20
-----------------------------
pki cert-find --certTypeSSLClient on
-----------------------------
Number of entries returned 20
-----------------------------
pki cert-find --certTypeSSLServer off  (Returns 1 when we have 1 cert with nsCertEmail)
---------------
0 entries found
---------------
[root@dhcp207-176 dogtag]# pki cert-find --certTypeSSLServer on
---------------
0 entries found
---------------
[root@dhcp207-176 dogtag]# pki cert-find --certTypeSubEmailCA off
---------------
0 entries found
---------------
# pki cert-find --certTypeSubEmailCA on
---------------
0 entries found
---------------
# pki cert-find --certTypeSubSSLCA off
---------------
0 entries found
---------------
# pki cert-find --certTypeSubSSLCA on
---------------
0 entries found
---------------

From the above output we can see that Number of entries that should be returned are not consistent across the above netscape switches. I would expect that either all the above options to pki cert-find do not show any certs or show certs which do not have any Netscape Extensions.

  1. When we provide some junk value to --cert* options they seem to do default search and return first 20 certs , instead it should return error asking the user to provide the right option

Example:

pki cert-find --certTypeSecureEmail dlfkdf131
-----------------------------
Number of entries returned 20
-----------------------------
pki cert-find --certTypeSSLClient dlfkdf131
-----------------------------
Number of entries returned 20
-----------------------------
pki cert-find --certTypeSSLServer dfdfdfddffdf
-----------------------------
Number of entries returned 20
-----------------------------
pki cert-find --certTypeSubEmailCA dfdfadfadsfadf
-----------------------------
Number of entries returned 20
-----------------------------
pki cert-find --certTypeSubEmailCA ldk32342342342343
-----------------------------
Number of entries returned 20
-----------------------------

Versions:
pki-ca-10.2.0-0.1.20140520T0344zgita9b44bd.fc20.noarch (Build date: Tue 20 May 2014 12:31:40 AM EDT)
pki-tools-10.2.0-0.1.20140520T0344zgita9b44bd.fc20.x86_64 (Build Date: Tue 20 May 2014 12:31:40 AM EDT)

proposed Milestone 10.2.2.

Proposed Milestone: 10.2.2 (per CS Meeting of 09/17/2014)

Per Dogtag 10.2.X meeting of 01/14/2015: Milestone 10.2 Backlog

Per 10.2.3 TRIAGE meeting of 02/26/2015: 10.3

NOTE: Moved from 10.2 Backlog since it was not a documentation/man page issue.

Per Bug Triage of 05/05/2016: 10.4

Metadata Update from @mrniranjan:
- Issue set to the milestone: UNTRIAGED

Metadata Update from @mharmsen:
- Custom field feature adjusted to None
- Custom field reviewer adjusted to None
- Custom field version adjusted to None
- Issue close_status updated to: None
- Issue set to the milestone: FUTURE (was: UNTRIAGED)

Per 10.5.x/10.6 Triage: FUTURE

mharmsen: Netscape Extensions are very old and are probably not used that frequently if ever any more

Maybe we should just close this WONTFIX. It's (these days) such an obscure use case.

Per offline triage, these extensions are obsolete and hardly used. Closing WONTFIX.

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

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

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