Red Hat Bugzilla – Bug 501342
RE_ENROLL does not reset after a re-enrollment is done.
Last modified: 2015-01-04 18:38:38 EST
Description of problem:
IF the RE_ENROLL flag was original set to NO and then an TPS Agent set the flag to YES after one enrollment the flag should reset back to NO. This is not happening for RE_ENROLL.
Works correctly for PIN_RESET
Version-Release number of selected component (if applicable):
CS 8.0 Beta 2
Steps to Reproduce:
1.Set the default Renroll and Pin reset flags to NO in the tps CS.cfg files
2.Enroll a token. Have a TPS agent change the RE_ENROLL flag from No to YES.
3.Re-enroll the token. That works.
4. Check the Flag status and notice RE_ENROLL is not reset back to NO
Can re-enroll as many times as you want to
Can only re-enroll once
Pin reset works fine
just for the record:
The behaviour is as expected by design. This is a policy that allows
the agent to set for the token whether re-enrollment is allowed or not.
There is no implication in the design to allow this re-enollment to take
place only once.
Although I could see the use for it.