Red Hat Bugzilla – Bug 494981
CS 8.0 Alpha -- When Renrollment policy is set (RE_ENROLL) then the error message display erroneously specifies the card is suspended.
Last modified: 2009-09-02 05:58:22 EDT
Created attachment 338808 [details]
Renroll error (logs and screenshot)
Description of problem:
Version-Release number of selected component (if applicable):
When Renrollment policy is set (RE_ENROLL) then the error message display erroneously specifies the card is suspended. See the attached zip which has the tps debug and error log and the screenshot of the message
Steps to Reproduce:
1. Through the Agent page of the TPS specifiy the RE_ENROLL to be false.
2.Try to enroll a formatted token.
Incorrect error message referencing the card is suspended.
Error message referencing the card can't be re enrolled.
Proposed error message change:
RCS file: /cvs/dirsec/esc/src/app/xul/esc/chrome/locale/en-US/esc.properties,v
retrieving revision 1.7
diff -r1.7 esc.properties
< errorTokenSuspended=Your smart card has been suspended.
> errorTokenSuspended=You are not allowed to perform this operation with this sm
Changing product from Certificate System to Red Hat Enterprise 5. Rebase of
ESC to version 1.1.0 to pick up present and future Certificate System v8 fixes.
Setting ack requests.
Setting devel ack.
Comment #1 +mharmsen
$ cvs commit esc.properties
Checking in esc.properties;
/cvs/dirsec/esc/src/app/xul/esc/chrome/locale/en-US/esc.properties,v <-- esc.p
new revision: 1.8; previous revision: 1.7
Performed token enrollment using Gemalto 64K smart cards on Rhel 5.3
coolkey version: coolkey-1.1.0-6.el5 (latest from RHEL5.3 BaseOS)
esc version: esc-1.1.0-9.el5 (cs 8.0 build)
1. Enroll token#1 fo user#1.
2. Format token#1.
3. tps agent page set policy for token#1 to be RE_ENROLL=NO
4. Enroll token#1 for user#2, enrollment is successful.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.