Thank you so much. I am in the same situation exactly. return null is the key
in getPasswordAgain(info). If you put a breakpoint here you can see it enters
here to ask the password again.
I think, it will also work if we implement a logic of showing a dialog to ask
the user the password again,
Thanks for the reply, Robert!
We're using OpenSC 0.16.0 and it's working well so far. The problem turned out
to be exactly what you suggested.
The JSS PK11Token login method takes a password callback handler. The handler
has a getPasswordAgain method that's used for retries, and returning
On 10/07/2016 06:56 PM, Ernie Kovak wrote:
Hello -
We're using JSS4 and NSS 3.24 with an OpenSC module to interact with a DoD CAC.
CACs will lock after 3 consecutive bad PIN entries. We're finding that if the
user enters a bad PIN even once, that hard limit is exceeded and the card is
On Friday, October 7, 2016 at 7:56:29 PM UTC-6, Ernie Kovak wrote:
I replaced the OpenSC module with an ActivClient module (acpkcs211.dll) and
that module does not lock the card. I've posted a query to the OpenSC forum
asking about this.
However, ActivClient displays its own PIN prompt dialog,
Hello -
We're using JSS4 and NSS 3.24 with an OpenSC module to interact with a DoD CAC.
CACs will lock after 3 consecutive bad PIN entries. We're finding that if the
user enters a bad PIN even once, that hard limit is exceeded and the card is
locked.
I've searched through NSS to see if
5 matches
Mail list logo
