#2566 Return nicknames and token of system certs during installation of a clone
Closed: migrated by dmoluguw. Opened by gkapoor.

Make a request to getTokenInfo servlet like: curl -kv -L --anyauth
https://pki1.example.com:31443/ca/ee/ca/getTokenInfo

Steps to Reproduce:

1.Configure clone
2.Make a request to getTokenInfo servlet like: curl -kv -L --anyauth
https://pki1.example.com:31443/ca/ee/ca/getTokenInfo

Actual results:

[root@pki1 ca]# curl -kv -L --anyauth
https://pki1.example.com:31443/ca/ee/ca/getTokenInfo
* About to connect() to pki1.example.com port 20443 (#0)
* Trying 10.65.201.82...
* Connected to pki1.example.com (10.65.201.82) port 20443 (#0)
* Initializing NSS with certpath: sql:/tmp/abc
* skipping SSL peer certificate verification
* NSS: client certificate not found (nickname not specified)
* SSL connection using TLS_RSA_WITH_AES_256_CBC_SHA
* Server certificate:
*     subject:
CN=pki1.example.com,OU=topology-02-CA,O=topology-02_Foobarmaster.org
*     start date: Sep 09 13:54:09 2016 GMT
*     expire date: Aug 30 13:54:09 2018 GMT
*     common name: pki1.example.com
*     issuer: CN=CA Signing
Certificate,OU=topology-02-CA,O=topology-02_Foobarmaster.org
> GET /ca/ee/ca/getTokenInfo HTTP/1.1
> User-Agent: curl/7.29.0
> Host: pki1.example.com:20443
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Server: Apache-Coyote/1.1
< Content-Type: text/html;charset=utf-8
< Content-Language: en
< Content-Length: 993
< Date: Thu, 22 Sep 2016 17:44:10 GMT
<
* Connection #0 to host pki1.example.com left intact
<html>
<head>
    <title>Apache Tomcat/7.0.69 - Error report</title>
    <style><!--H1 {fo
nt-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-siz
e:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#
525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;bac
kground-color:#525D76;font-size:14px;} BODY
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {
font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px
;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style>
</head>
<body>
<h1>HTTP Status 404 - /ca/ee/ca/getTokenInfo</h1>
<HR size="1" noshade="noshade">
<p>
    <b>type</b> Status report
</p>
<p>
    <b>message</b>
    <u>/ca/ee/ca/getTokenInfo</u>
</p>
<p>
    <b>description</b>
    <u>The requested resource is not available.</u>
</p>
<HR size="1" noshade="noshade">
<h3>Apache Tomcat/7.0.69</h3>
</body>
</html>

Expected results:

On the command-line, Nicknames should be returned successfully
<XMLResponse>
<Config>
    <name>cloning.signing.nickname</name>
    <value>caSigningCert cert-pki-ca</value>
</Config>
<Config>
    <name>cloning.ocsp_signing.nickname</name>
    <value>ocspSigningCert cert-pki-ca</value>
</Config>
<Config>
    <name>cloning.subsystem.nickname</name>
    <value>subsystemCert cert-pki-ca</value>
</Config>
<Config>
    <name>cloning.audit_signing.nickname</name>
    <value>auditSigningCert cert-pki-ca</value>
</Config>
<Config>
    <name>cloning.module.token</name>
    <value>NHSM6000-OCS</value>
</Config>
<Status>0</Status>
</XMLResponse>

See also #1473.

Metadata Update from @gkapoor:
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

Metadata Update from @mharmsen:
- Custom field feature adjusted to ''
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field version adjusted to ''
- Issue close_status updated to: None
- Issue set to the milestone: 10.4 (was: 0.0 NEEDS_TRIAGE)

Per CS/DS Meeting of August 7, 2017, it was determined to move this issue from 10.4 ==> FUTURE.

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

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

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)

Metadata