Using Login Notification to create access log

kklosson · Post by **kklosson** » Sun Jan 11, 2009 12:14 pm

What am I missing on this?

I created a Login Notification and in the Rule for when the notification is created, I added statements to CREATE an access record for the person logging in. So far, nothing. Am I correct in assuming that the Login Notification is created with each Login? Does the Notification have to be SENT (I tried that too)? I'm missing something here about when this notification occurs.

I don't see login notifications being used in any of the same apps. No help there.

tford · Post by **tford** » Sun Jan 11, 2009 12:51 pm

Following login notification rules work for me:

1) Creates a log of users and updates certain attributes of the LoggedInRegularUser BO:
CREATE UsersLog WITH UsersLog.IpAddress=LoginNotification.RemoteAddress,
UsersLog.Name=LoginNotification.LoginName,
UsersLog.Time=CURRENT_TIMESTAMP,
UsersLog.LogType='Login',
UsersLog.AccessLevelName=LoggedInSystemUser.AccessLevel

LoggedInRegularUser.LastLoginTime=CURRENT_TIMESTAMP

LoggedInRegularUser.LastRemoteAddress=LoginNotification.RemoteAddress

INCREASE LoggedInRegularUser.NbrLogins BY 1

2) Sends an administrator a message that a user has logged into the system. This can be enabled / disabled via a SystemSetting:
If SystemSettings.EmailLogins='Yes'
Then
SEND OutgoingEmail_Admin_UserLoggedIn TO SystemSettings

Tom

kklosson · Post by **kklosson** » Sun Jan 11, 2009 1:20 pm

Hmmm. That seems to be what I'm doing. I have a rule to create the Access Log record in the Login Notification. I can't get much from the log either.

kklosson · Post by **kklosson** » Sun Jan 11, 2009 1:28 pm

So my rule is simply:

CREATE AccessLog WITH
AccessLog.Candidate=LoggedInCandidate,
AccessLog.DateTime=TIMESTAMP(),
AccessLog.IPAddress=LoginNotification.RemoteAddress,
AccessLog.LoginID=LoginNotification.LoginName

I don't even see anything being logged...

tford · Post by **tford** » Sun Jan 11, 2009 1:30 pm

Feel free to post your rule.

I'm assuming you are placing the rule in the section "When LoginNotification is received"

Tom

tford · Post by **tford** » Sun Jan 11, 2009 1:32 pm

I'm thinking you are putting the rule under AccessLog BO instead of the LoginNotification.

kklosson · Post by **kklosson** » Sun Jan 11, 2009 1:32 pm

No, I'm placing it in When Created, though I tried the other.

Do system settings need to be set to email logins?

kklosson · Post by **kklosson** » Sun Jan 11, 2009 1:36 pm

This is all I have in the log...

-Exception while calculating the action CREATE AccessLog WITH AccessLog.Candidate=LoggedInCandidate,AccessLog.DateTime=TIMESTAMP(),AccessLog.IPAddress=LoginNotification.RemoteAddress,AccessLog.LoginID=LoginNotification.LoginName

tford · Post by **tford** » Sun Jan 11, 2009 1:36 pm

It should be in the "When LoginNotification is received" section.

Do system settings need to be set to email logins?

Yes, you need to create a SystemSettings instance in the BO and the SystemSettings BO needs to be intelligent to send emails of logins.

Tom

tford · Post by **tford** » Sun Jan 11, 2009 1:38 pm

TIMESTAMP(),

If you look at my rule, the proper syntax is CURRENT_TIMESTAMP

kklosson · Post by **kklosson** » Sun Jan 11, 2009 1:39 pm

Well,

I don't need to send any emails, I just want to log the even in the database.

On TIMESTAMP, I found that the rule would not validate with ()

This may be the heart of the problem...

tford · Post by **tford** » Sun Jan 11, 2009 1:43 pm

Since you seem to be interested in Login stuff, I use the following rules to:
1) I keep a log of bad login attempts
2) I get an immediate email when it occurs so that I can contact a user that is having a problem.

Place the following rule in the "When LoginAttemptNotification is received" section of LoginAttemptNotification

If EXISTS SystemUser WHERE (SystemUser.LoginName=LoginAttemptNotification.LoginName) Then
CREATE UsersFailedLogins WITH UsersFailedLogins.IpAddress=LoginAttemptNotification.RemoteAddress,UsersFailedLogins.Name=LoginAttemptNotification.LoginName,UsersFailedLogins.Time=CURRENT_TIMESTAMP,UsersFailedLogins.Reason='Invalid Password'

Else

CREATE UsersFailedLogins WITH UsersFailedLogins.IpAddress=LoginAttemptNotification.RemoteAddress,UsersFailedLogins.Name=LoginAttemptNotification.LoginName,UsersFailedLogins.Time=CURRENT_TIMESTAMP,UsersFailedLogins.Reason='Invalid User Name'

I then have a rule for the UsersFailedLogins BO:
If UsersFailedLogins IS NEW Then
SEND OutgoingEmail_InvalidLogin TO SystemSettings

Tom

kklosson · Post by **kklosson** » Sun Jan 11, 2009 1:43 pm

And there you go...

I was using TIMESTAMP, instead of CurrentTimeStamp.

Made all the difference.

Thank you for helping me through this. You're a big asset!