[Tickets #7829] Re: Improve / standarize / clean up log messages

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7829
------------------------------------------------------------------------------
  Ticket             | 7829
  Updated By         | thomas at gelf.net
  Summary            | Improve / standarize / clean up log messages
  Queue              | Horde Groupware Webmail Edition
  Version            | 1.2.1
  Type               | Enhancement
  State              | New
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


thomas at gelf.net (2009-01-07 14:32) wrote:

One more comment:

IMP::loginLogMessage() is doing a great job for most tasks, however it  
is not handling all events I'm interested in ;-) What I noticed is  
that when using the _username_hook_frombackend-Hook,  
IMP::loginLogMessage() is logging the "wrong" username, it is using  
data from $_SESSION['imp']['user'] (Auth::getAuth() is showing the  
corrected one).

To be more precise, I'm applying String::lower() in my  
_username_hook_frombackend, and I'm also adding our main domain if no  
domain has been given. I agree that it would be interesting to also  
have the "original" username in my logs, but this could be an  
addition. If a User is logging in as Joe I would like to have

> Login success for joe at mycompany.tld [1.2.3.4]...

or

> Login success for joe at mycompany.tld (Joe) [1.2.3.4]...

but not just

> Login success for Joe [1.2.3.4]...

to be written to my logs.