Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 472509

Summary: TPS PKI services inaccessible on Fedora.
Product: [Retired] Dogtag Certificate System Reporter: Kashyap Chamarthy <kchamart>
Component: TPSAssignee: Ade Lee <alee>
Status: CLOSED DUPLICATE QA Contact: Chandrasekar Kannan <ckannan>
Severity: high Docs Contact:
Priority: high    
Version: 1.0CC: alee, benl, jmagne
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-12-08 20:18:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 443788    

Description Kashyap Chamarthy 2008-11-21 10:06:15 UTC 
Description of problem:
Unable to launch TPS services after installing it on Fedora 8.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Prerequisites:

All the system prerequisites and runtime tools required for the Dogtag PKI.


Steps to Reproduce:
1.Install the TPS subsystem.
2.Start the service(service pki-tps start)
3.Now try to launch TPS PKI services by accessing https://localhost:7889

  
Actual results:

1. Firefox can't establish a connection to the server at localhost:7889

Expected results:

1. TPS PKI services should be launched.

Additional info:

(1) CA, RA, DRM, OCSP services are running, while I tested the above.

(2) tps-error and tps-debug logs emit the below statements:

A ca certificate nicknamed "[HSM_LABEL][NICKNAME]" could NOT be found in 
the certificate database for connection 1!
A tks certificate nicknamed "[HSM_LABEL][NICKNAME]" could NOT be found 
in the certificate database for connection 1!
 A drm certificate nicknamed "[HSM_LABEL][NICKNAME]" could NOT be found 
in the certificate database for connection 1!
Comment 1 Ade Lee 2008-12-08 20:18:35 UTC 

*** This bug has been marked as a duplicate of bug 453508 ***