LoginNotification Additional Attributes

syndeo

Ok thanks for that.

The documentation states that we can add other attributes to the LoginNotification. What is purpose of this? Can we capture other details of the client? eg browser or some sort of unique ID.

I am looking at implementing 2FA which would require the user to authenticate the 2FA only once every 24 hours on a particular browser/machine. I can capture the browser information using JS in localStrorage, but how would I return that to AIM to check if the 24 hrs have passed or not? Is a java plugin the only solution?

I was also thinking that a JS could change the value of an HTML input (an AIM attribute) with the localStorage data which would be saved to the database by way of business object rule or process. Obviously the BO would have to be in context or we could use the special session (non persistent) BO.

aware_support3

The LoginNotification is an object that automatically collects the information in the default LoginNotification attributes.

syndeo The documentation states that we can add other attributes to the LoginNotification. What is purpose of this? Can we capture other details of the client? eg browser or some sort of unique ID.

The sessionId should already be collected by the Notification object. Does that not provide you with a unique ID?

syndeo I can capture the browser information using JS in localStrorage, but how would I return that to AIM to check if the 24 hrs have passed or not? Is a java plugin the only solution?

Add a date time attribute to the Notification object. Set it to be CURRENT_TIMESTAMP by default.

If you want to keep all of these details in context for the LoggedInUser create an object When LoginNotficationIsReceived and add a relationship to the user who is logged in.

syndeo

Ok, yes no worries. So there is no real need to add new attribute to the LoginNotification if you are going to save the data in a BO. for example. Wouldn’t you just do this

LogBO.LoginName = LoginNotification.LoginName
LogBO.Time = CURRENT_TIMESTAMP

or does creating the LoginNotification attribute a better way of doing it?

Regarding the session ID. whilst it is unique, it does not persist on the client machine. It changes every time you refresh the browser and thus adds another record to the LogBO by obtaining new data from the LoginNotification.

aware_support3

syndeo does creating the LoginNotification attribute a better way of doing it?

No, the LoginNotification is not persisted.