Closed jugmac00 closed 5 years ago
Just go to the error_log
object and add Unauthorized
to the list of ignored exceptions.
@dataflake Thanks a lot for this quick and obviously perfect answer.
I just updated the error_log
object and I see no more new Unauthorized
errors in my log file.
I'd like to wait a couple of hours, and if no more occurrences appear, I'll close this ticket.
P.S.: I will have a look at the documentation and maybe add a paragraph about how to silence the log entries.
By the way, the reason you see those now and not before is simply a difference in processing when an Unauthorized is being hit. The other code simply swallowed those and never let them propagate. There's no right or wrong here and nothing to worry about, it's just different.
I have never found any good reason to not ignore Unauthorized in the error log. And if you need to debug them just take them out of that ignore list for a time.
In an attempt to move forward to Zope 4 / Python 3, I replaced the existing authentication stack (CookieCrumbler/SimpleUserFolder/CMFCore) with PluggableAuthService.
It works as expected, but since then Zope's event log gets spammed with following error messages:
There are three main "causers" for these log entries:
I can and did update the url for the uptime checks to something like: https://xxx.xxx.de/acl_users/cookie_auth/login_form which then throws no more error.
Obviously, I cannot tell my users to type that long url - they usually just enter the domain.
Why do unauthorized exceptions now get logged? And is there anything I can do to prevent these messages?
Configuration: