User tests: Successful: Unsuccessful:
Database errors are uncaught/unmanaged in the authentication cookie plugin right now. This PR adds error handling for the plugin by catching exceptions thrown by the database layer and deciding how to proceed.
Generally just make sure the plugin still works.
Labels |
Added:
?
|
Labels |
Added:
?
|
Easy | No | ⇒ | Yes |
Category | ⇒ | Authentication Plugins |
Milestone |
Added: |
Disagree on not being interested in failures. Suggest logging the error to inform webmaster.
JDatabase already has logging mechanisms built into the driver execute methods, you just need to have a logger enabled and listening to the databasequery
category. So I don't think we need to duplicate that into the plugin here. That leaves this PR to just catch exceptions and decide whether the error is fatal to execution or if it can keep going.
@mbabker Please provide clear test instructions. With 2 people we have been unable to figure out how this should be tested. Thanks.
I don't have anything to give for instructions. I don't know how you can actually trigger the errors that are being caught here in normal system operation to validate "sensitive" data is masked or the error conditions are correctly executed, the only thing I can suggest is that you enable cookie authentication and make sure the success paths work right.
In that case, I can say testing is OK. We tried a lot of ways to get an error but things kept working :)
:-) same here - didnĀ“t get errors
Status | Pending | ⇒ | Ready to Commit |
RTC Thanks for testing and coding
Labels |
Added:
?
|
Status | Ready to Commit | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2015-06-09 19:49:05 |
Closed_By | ⇒ | roland-d |
Labels |
Removed:
?
|
@test works for me
but not so sure how to simulate properly i've just mispelled some fieldname in some queries