Bug 498999 - CS 8.0 Beta -- Unable to preform a master key change over
Summary: CS 8.0 Beta -- Unable to preform a master key change over
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Dogtag Certificate System
Classification: Retired
Component: TPS
Version: 1.1
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Christina Fu
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On:
Blocks: 443788
TreeView+ depends on / blocked
 
Reported: 2009-05-04 18:44 UTC by Sean Veale
Modified: 2015-01-04 23:38 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-05-06 14:12:01 UTC
Embargoed:


Attachments (Terms of Use)
log and config files (24.53 KB, application/zip)
2009-05-04 18:44 UTC, Sean Veale
no flags Details

Description Sean Veale 2009-05-04 18:44:23 UTC
Created attachment 342349 [details]
log and config files

Description of problem:

After preforming the key change over procedure documented in section 6.9.5 of the admin guide I'm unable to establish a secure channel between the card and tps. 

From the tps error log
[2009-04-30 17:31:28] 1435eb80 RA::ComputeSessionKey - Failed connecting to TKS after 3 retries
[2009-04-30 17:31:28] 1435eb80 RA_Processor::SetupSecureChannel - Failed to create a secure channel - potentially due to an RA/TKS key mismatch or differing RA/TKS key versions.
[2009-04-30 17:31:28] 1435eb80 RA_Processor::UpgradeApplet - channel creation failure

There is some doc bugs that I'll file as a separate report



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


How reproducible:
Always

Steps to Reproduce:
1. Follow 6.9.5 to preform a key changeover
2.Attempt to enroll a card
3.
  
Actual results:
Failed to create secured channel

Expected results:
Able to enroll the token

Additional info:

Using safenet 330J cards. 

Added tps debug/error log , tps and tks config files and the commands I sent to preform this process.

Comment 1 Sean Veale 2009-05-06 14:12:01 UTC
This was user error and is not a bug.

Sean


Note You need to log in before you can comment on or make changes to this bug.