New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client Cert PKCS#11 - UI/Exception Handling #3261
Comments
By handled better, do you mean it shouldn't be being logged? The user is informed (AFAICT) about the possible cause(s) of the problem. |
I just figured that the exception(s) could be caught and a more user friendly message displayed instead of just stack trace. Or, even better if the button wasn't active until there is actually something to add to the keystore. (In which case there shouldn't be any exception to handle, or at least not with the same cause [try to load a non-existent key.]) |
Ah, you mean in the log file? It's not logging a more friendly message because it's already shown in the UI (and the current code it's only used by the UI). Unless no message is being shown?? Not sure we are able to tell if there's a key (or not) without trying to add it? |
Your right there is an error dialog in the UI, which means the exception could probably to go DEBUG instead of WARN. (Or we make a user friendly WARN message and put the details in DEBUG). We could probably at least check that there is a PIN code entered ... unless there are pinless/passwordless implementations... |
That's WARN to be logged by default, as that's useful if we need more info about the problem. Yeah, maybe. |
Refactor OptionsCertificatePanel slightly to display an error (but not log an exception) if the PKSCS#11 PIN field is blank when the user clicks "Add to Keystore". If a PIN is present then the existing behavior is still observed (display error message and log exception). Fixes zaproxy#3261
Refactor OptionsCertificatePanel slightly to display an error (but not log an exception) if the PKSCS#11 PIN field is blank when the user clicks "Add to Keystore". If a PIN is present then the existing behavior is still observed (display error message and log exception). Fixes zaproxy#3261
Refactor OptionsCertificatePanel slightly to display an error (but not log an exception) if the PKSCS#11 PIN field is blank when the user clicks "Add to Keystore". If a PIN is present then the existing behavior is still observed (display error message and log exception). Fixes zaproxy#3261
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
If you enable client certs then goto the PKCS#11 tab and hit "Add to Keystore" you get an exception.
It should be handled better, or perhaps the button shouldn't be active until there's something to add.
The text was updated successfully, but these errors were encountered: