01-06-2010 08:08 AM
Hi all,
Am I missing something really simple? Is there a way to see the source of a failed login attempt in the authentication logs on an IronPort C150?
For instance: Wed Jan 6 10:57:39 2010 Info: User XXX failed authentication.
Solved! Go to Solution.
01-24-2010 03:17 PM
Hello Robert,
Did you try to set the logging level of your authentication logs to "debug"?
I'm not sure if the source address is noted but it logs a terrible lot of info. (in my case: I could retrieve the used LDAP authentication queries from the log for further testing)
Steven
01-20-2010 07:21 AM
It would seem that this is not a possibility.
01-24-2010 03:17 PM
Hello Robert,
Did you try to set the logging level of your authentication logs to "debug"?
I'm not sure if the source address is noted but it logs a terrible lot of info. (in my case: I could retrieve the used LDAP authentication queries from the log for further testing)
Steven
01-28-2010 05:40 AM
Hi Steven,
Thanks for the help, mate. I might be missing something here but setting the log level on the Authentication logs to debug then committing the changes doesn't display any more information than the informational log level. Was there something else that needed to be changed?
01-28-2010 12:30 PM
If you are referring to the SMTP authentication (which can also use LDAP) the connecting source would look as follows:
Authentication attempts made during inbound connections (in order to gain relay access) are logged in the mail_logs when successful and unsuccessful. All relevant entries will be associated with the ICID in question.
Outbound SMTP Authentication
When SMTP authentication is required for deliveries to a specific host (configured via an "Outgoing" SMTP authentication profile and an SMTP route referencing said profile), both successful and unsuccessful authentication attempts will be logged in the mail_logs. All entries will be associated with the DCID in question.
01-28-2010 12:36 PM
Negative sir. We're talking about two different log files.
Thanks for the reply!
01-28-2010 02:16 PM
So are you referring to the user authentication log when one tries to connect to the IronPort GUI?
If that is so the gui_logs show the detail whom tried to login and from where? Can you give me more details as to which log your referring to?
01-29-2010 05:14 AM
It's the authentication logs. #4 as seen in the pic below. Typical lines of output will say:
Fri Jan 29 04:13:14 2010 Info: User XXX failed authentication.
Fri Jan 29 08:10:21 2010 Info: User XXX was authenticated successfully.
But nothing else. Seems to handle both GUI and CLI login attempts. What brought this up is at one point we saw a lot of failed login attempts in this log from what appeared to be a dictionary attack.
01-29-2010 05:36 AM
In that authentication log you can specify a different log level
Peter
__________________________________________________________________________________________
Log Level:
Critical (The least detailed setting. Only errors are logged.) | |
Warning (All errors and warnings created by the system.) | |
Information (Captures the second-by-second operations of the system. Recommended.) | |
Debug (More specific data are logged to help debug specific problems.) | |
Trace (The most detailed setting, all information that can be is logged. Recommended for developers only.) |
__________________________________________________________________________________________
01-29-2010 05:39 AM
Hiya Peter,
Yeah, we did that and committed the changes. Only no additional information was shown in the log. Thus my message above "It would seem that this is not a possibility." I guess I was just hoping that I was missing something really stupid.
Thanks all!
01-29-2010 05:48 AM
Robert,
I think the best is to ask support. I have tried this on our testmachine and nothing more is logged.
Peter
01-29-2010 05:49 AM
Thanks for confirming, Peter. I'll give the folks at support a call.
01-29-2010 11:06 AM
All logs via the CLI are logged in cli_logs. All GUI logs are logged in gui_logs. From what I gather, you are looking is in either one of the two gui_logs or cli_logs.
If someone was trying to attempt to login to the appliance. The Authentication log only will display if it was successful or not and the details of access via GUI and CLI are logged as I mentioned above.
01-29-2010 11:10 AM
Hi Fraidoon,
Ahhhh, that makes sense. So simply look at the time of successful/unsuccessful login attempt in the Authentication log and try to see if there's a matching entry in either the CLI or GUI log for more information?
01-29-2010 11:23 AM
Hello Robert,
You are correct.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide