You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 19, 2020. It is now read-only.
Please provide any additional information below.
Hello Frank,
I have a request for the picture feature in both identification and id+auth
method.
I do need the picture for my application, but reading the picture from the
card and uploading the 4K might be slow for some users. Thus, I started to
think of a method to ask the picture only on certain conditions (like the
card is already known in the system).
The ugly solution would be to keep the applet as is and make two
operations, but no, this would not be a good idea.
Would it be possible to have a small improvement of the protocol?
Instead of only having the "FinishedMessage" at the end of the transaction,
it would require to handle a new type of message like "NeedMoreData" with
options (or not) to have now the picture.
What do you think? It would save my users bandwidth and some precious
milliseconds, and milliseconds are important :D
Original issue reported on code.google.com by sbuyss...@gmail.com on 18 Feb 2010 at 11:31
The text was updated successfully, but these errors were encountered:
Actually the current eID Applet protocol already allows this kind of runtime
behavior (i.e. for some users ask for photo or not). Right now the eID Applet
Service implementation is kind of static towards eID Identification
configuration. You configure via some init-param like IncludeAddress,
IncludePhoto what you want to retrieve. What we need is something like
IdentificationService that allows the server-side to decide at runtime what
exactly to request for.
Original comment by frank.co...@gmail.com on 14 Aug 2010 at 6:32
Original issue reported on code.google.com by
sbuyss...@gmail.com
on 18 Feb 2010 at 11:31The text was updated successfully, but these errors were encountered: