Open rrightwrong opened 5 years ago
Pin could be being cached in the cards middleware.
Which card and middleware?
Try with app.hancockapp.com (select require smart card under transaction options) and let me know if you observe same thing.
I bet what is happening is your middleware caches pin per session.
@rrightwrong You can try to call crypto.logout()
after key using
Hey Ryan ! My web application uses USB Smart Card for reading of document signing certificates. While signing using WebCrypto (with FortifyApp) the PIN is automatically asked but only once. The next time(without unplugging the USB) if I use the same certificate for signing, the PIN is not asked but the function gets through successfully.
Assuming, the PIN is cached at some layer, is there any method to prevent caching of smart card PIN or forcing the PIN validation every time the signing is done. Is yes, how?