Token renewal is not working
Steps to Reproduce:
1. Format and enroll a smartcard token 2. Change the policy of the token to RENEW=YES 3. Enable transition 4:4 4. Enroll the token again
Actual results:
Token is re-enrolled, new certificates are issued for the token
Expected results:
Certificates on the token should be renewed
Per CS/DS Meeting of 09/14/2015 - 10.3
Closing for the following reason:
Works for both myself and cfu.
We tried the simple two cert profile and then came back and request a renewal in the TPS UI. The logs indicate the renewal proceeded fine.
Snippet:
TPSEnrollProcessor.enrollOneCertificate: detecting renewal mode! [18/Jan/2016:15:53:32]http-bio-8080-exec-1: TPSEnrollProcessor: We are in renewal mode, no work to do with the keys, in renewal the keys remain on the token. [18/Jan/2016:15:53:32]http-bio-8080-exec-1: TPSEnrollProcessor.enrollOneCertificate:: enrollment begins [18/Jan/2016:15:53:32]http-bio-8080-exec-1: TPSEnrollProcessor.enrollOneCertificate: Attempt to import cert data in recovery mode or renew mode! [18/Jan/2016:15:53:32]http-bio-8080-exec-1: TPSEnrollProcessor.enrollOneCertificate:: renewing: new cert b64 =MIIDazCCAlOgAwIBAgIBGjANBgkqhkiG9w0BAQsFADBHMSQwIgYDVQQKDBtsb2NhbGRvbWFpbiBTZWN1cml0eSBEb21haW4xHzAdBgNVBAMMFkNBIFNpZ25pbmcgQ2VydGlmaWNhdGUwHhcNMTYwMTE4MjM1MzMyWhcNMjEwMTE2MjM1MzMyWjAxMRcwFQYDVQQKDA5Ub2tlbiBLZXkgVXNlcjEWMBQGCgmSJomT8ixkAQEMBmptYWduZTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALFOCRH92vEq16A0AdSJ/fWJOnronSdjF7xL2r4o27F/iis0D9kBLUE/b6rkWraqn5zVUHRNAYPHRquSfSah3Q27RtC7Z2daoJkIyftVIKMKBpdJyH0r0BgVEF546kjrPRCM7Mk3LbrkLHc46haD114UKpBiAY+AAAg8fLambWc4QPCpWI4IpgImYqpQDaa0UinRqTwYHeiIii282BgRyYwboA9MJjVb8FNp5Nots8cHMIqWHBLK7V/1QCDfA8rFbnC5EYcspdTDWWV2C/FjzdW5sC+UBLRRjYgti1hQlUywiGlROn8eyWbpH9ufoIQfXstYUMpiQXHEGoFoZeRM5GMCAwEAAaN4MHYwDgYDVR0PAQH/BAQDAgbAMBkGA1UdEQQSMBCBDiRyZXF1ZXN0Lm1haWwkMB0GA1UdDgQWBBRigObNpt870cerS7qnVIn0hysscjAfBgNVHSMEGDAWgBSEP42ZJlEn/X+Lmoq235S7fDN5XzAJBgNVHRMEAjAAMA0GCSqGSIb3DQEBCwUAA4IBAQAv3ND8wnreMGngV3y8fTu53iFYtgPt0s73nftTCJp7WXa3e8IwyevNGQ60M5jNKUPFS/OMBiDUzBL7tQ+c+aH9x/aVB7XP44DP46nzZLTftVooqf6VtLvRQMz1n5/COZRcwgkvUHQYrykbJaaDc2tq2kYViCPpvrgh2XE2676zMFLuANv7NIGkwifMOUxQxDMESq8Z2CS5uoYoI7A9/Y7ni/5gdKSEn5/hRqU6ua3vG4thm1craNFVX7FqZfxvO98uy7SZ3GmBoU8W97rejky7Kx6+1A5YeHRuAgqPKaIXazeGmcwmzVSZgfcNdjkDRek4qYfF8gTTBwHo1PV2wqMz [18/Jan/2016:15:53:32]http-bio-8080-exec-1: TPSEnrollProcessor.enrollOneCertificate:: renewing new cert retrieved
Metadata Update from @rpattath: - Issue set to the milestone: UNTRIAGED
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/2169
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.