Receiving 2 LoginAttemptNotifications

BobK

My application logs user logins, login attempts and logouts.

The following code is for 'When LoginAttemptNotification is received':

If EXISTS SystemUser WHERE (SystemUser.LoginName=LoginAttemptNotification.LoginName) Then
FIND SystemUser WHERE SystemUser.LoginName=LoginAttemptNotification.LoginName
ThisSystemUser.LastLoginAttempt=CURRENT_TIMESTAMP
ThisSystemUser.BadLogins=ThisSystemUser.BadLogins+1
ThisSystemUser.IPAddress=LoginAttemptNotification.RemoteAddress
CREATE LoginLog WITH LoginLog.IP=LoginAttemptNotification.RemoteAddress,LoginLog.LogType='LOGINBADPW',LoginLog.WebID=LoginAttemptNotification.LoginName,LoginLog.Description=LoginAttemptNotification.LoginName+' tried invalid password, bad attempts = ' + AS_STRING(ThisSystemUser.BadLogins)
Else
CREATE LoginLog WITH LoginLog.IP=LoginAttemptNotification.RemoteAddress,LoginLog.LogType='LOGINBADID',LoginLog.WebID=LoginAttemptNotification.LoginName,LoginLog.Description=LoginAttemptNotification.LoginName+' not in database'

When I tested this, I got 2 LoginLog records for each login attempt. Is there something wrong with my code, or are 2 LoginAttemptNotifications being generated?

Thank you.

aware_support

Can you trying splitting this rule in two and not using ELSE, i.e. rule with EXISTS and rule with NOT (EXISTS)

leopdurr

I am having the same problem this is my code

CREATE SystemLog WITH SystemLog.Username=LoginAttemptNotification.LoginName,SystemLog.DateLogin=CURRENT_TIMESTAMP,SystemLog.RemoteIP=LoginAttemptNotification.RemoteAddress,SystemLog.LogginAttemptStatus='Fail'

rocketman

Only two??

I get up to NINE loging notifications with Firefox users. Normally only 1 with Chrome and IE users - sometimes 2 with chrome.

I'm on the move but will post my code later. Having seen my logs, I can pinpoint the users who always seem to issue lots of login attempts - many of whom I know live in poor broadband areas and have put it down to browser/latency issues.

But if there's a better explanation, would love to hear it

Should add They seem to login/out immediately so don't tie up any session resources ... and of course might be totally unconnected with your problems guys