Project

General

Profile

Actions

Feature #160

closed

Provide Clear Feedback with respect to PIN-related problems in User Consents

Added by Detlef Hühnlein almost 12 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
High
Target version:
Start date:
12/08/2012
Due date:
% Done:

0%

Estimated time:
8.00 h
Reviewer:
Build Version:

Description

The demo application and/or the app should provide clear feedback in case of PIN-related problems (e.g. not activated PIN, CAN/PUK required).


Files

richclient_info.log (643 KB) richclient_info.log Patrik Schwieger, 03/26/2013 12:00 PM
Actions #1

Updated by Patrik Schwieger over 11 years ago

It seem's, that I catched that missing function?!

In any case where a wrong PIN is entered, nothing is displayed, we get repeatly the PIN dialog.
In case that a comfort reader is used with PIN pad and two faulty attemps were done already, the CAN is required.
But the Open eCard app does not start the dialog on the comfort reader. It simply fails like a wrong PIN input.

The attached log file shows some wrong PINs done with basis reader, but it was more than 3 times and the card was not locked.
The last were done with the comfort reader (PIN not entered successfully in terminal.) but during the last one, ther was no PIN input due to missing CAN request.

Actions #2

Updated by Tobias Wich over 10 years ago

  • Subject changed from Provide Clear Feedback with respect to PIN-related problems in Demo Application and/or App to Provide Clear Feedback with respect to PIN-related problems in User Consents
  • Target version set to 1.1.0

This concerns PinCompare and EAC/PACE

Actions #3

Updated by Tobias Wich over 10 years ago

  • Priority changed from Normal to High
Actions #4

Updated by Tobias Wich over 10 years ago

From TR-03124-1 sec. 3.6

As part of Online-Authentication and PIN Management, the eID-Client SHALL
  • inform the user about the current value of the retry counter of the PIN if PIN verification fails;
  • enable the user to retry PIN verification, and
  • enable the user to resume the PIN by entering the CAN if the PIN is suspended.
Actions #5

Updated by Detlef Hühnlein over 10 years ago

  • Estimated time set to 8.00 h
Actions #6

Updated by Tobias Wich over 10 years ago

  • Status changed from New to In Progress
  • Assignee set to Tobias Wich
Actions #7

Updated by Tobias Wich about 10 years ago

  • Assignee changed from Tobias Wich to Hans-Martin Haase
Actions #8

Updated by Tobias Wich about 10 years ago

  • Reviewer set to Tobias Wich

Localization is still missing, but logic seems good, so this part is already merged in 80e5726c11.

Actions #9

Updated by Hans-Martin Haase about 10 years ago

  • Status changed from In Progress to Review
Actions #10

Updated by Hans-Martin Haase about 10 years ago

  • Status changed from Review to Solved
Actions #11

Updated by Tobias Wich about 10 years ago

  • Status changed from Solved to Closed
Actions

Also available in: Atom PDF