Feature #9536
Improve logging of security related events
| Status: | Resolved | Start date: | 2010-08-31 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Robert Lemke | % Done: | 100% |
|
| Category: | Security | |||
| Target version: | TYPO3 Flow Base Distribution - 1.0 alpha 12 | |||
| PHP Version: | Complexity: | |||
| Has patch: |
Description
Security related actions and events should be logged into its own file / backend because
- they log data might be sensitive
- important information might drown in the amount of other messages
Additionally I'd like to see some hint if a user logged in or was re-authenticated due to an active token found in the session.
Associated revisions
[+FEATURE] FLOW3 (Security): Security events are logged to own file and more verbosively
Aside from the FLOW3 system log - whose file name is now "System.log" -
FLOW3 now writes security related log messages into its own log file
called "Security.log".
Furthermore, the logging advices now report more detailed information
about re-authentication and authentication redirects.
Change-Id: I8e59c1493ee55c01b3c13ec94cbefa42b1341c08
Resolves: #9536
History
#1 Updated by Robert Lemke almost 5 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Applied in changeset 84bb24831ba772c03ede2034cd0eb8d8aaf6304b.