Login Information Parser

Overview

The Smart Service, Import Login Audit, will read your login audit file(s) and populate a database with information about logins. This is provided mainly as an example (source code provided) as you may need to modify the smart service to make it work with your environment.

Requires a table named "logins" in the specified datasource. The example SQL is provided.
Inputs:
- datasourceName: The datasource where the login information will be populated
- date: The date suffix for the login_audit.csv* file to be read. If null, it reads the latest file.
Supports MySQL, Oracle and Microsoft SQL Server databases

Parents

John Stretton over 4 years ago

Eduardo Fuentes, are you familiar with an issue where this plugin fails to write a large portion of a particular day's login history? It seems like there are random days on which the login history is truncated. You can see in the table below that on some days (such as 7/1 or 6/17), the max time for a recorded login is very early in the day, and in fact I have confirmed that there are many more rows in the log file than what was written to the database for those days.

This also happened for 7/6, but I deleted the existing login history for 7/6 and reran the plugin, and it wrote all of the rows correctly. However, I tried this for 6/17 (twice) and both times it failed at exactly the same place where it stopped writing the first time.

I have just discovered that some users have been incorrectly deactivated for inactivity due to this issue, so any help would be much appreciated.

date count(*) max(time)
2020-07-06 763 23:48:05
2020-07-05 75 23:55:53
2020-07-04 54 23:17:39
2020-07-03 314 23:41:08
2020-07-02 587 23:59:27
2020-07-01 142 10:15:13
2020-06-30 687 23:48:19
2020-06-29 523 15:20:02
2020-06-28 102 23:53:13
2020-06-27 88 23:45:35
2020-06-26 586 23:45:32
2020-06-25 694 23:46:02
2020-06-24 676 23:58:31
2020-06-23 557 19:02:40
2020-06-22 790 23:44:43
2020-06-21 77 23:48:33
2020-06-20 61 23:24:34
2020-06-19 642 23:51:23
2020-06-18 654 23:50:03
2020-06-17 72 07:50:31
2020-06-16 711 23:59:06
2020-06-15 705 23:37:09
2020-06-14 64 23:36:59
2020-06-13 57 23:37:49
2020-06-12 527 23:38:02
- Cancel
- Up 0 Down
- Reply
- More
- Cancel

Comment

John Stretton over 4 years ago

Eduardo Fuentes, are you familiar with an issue where this plugin fails to write a large portion of a particular day's login history? It seems like there are random days on which the login history is truncated. You can see in the table below that on some days (such as 7/1 or 6/17), the max time for a recorded login is very early in the day, and in fact I have confirmed that there are many more rows in the log file than what was written to the database for those days.

This also happened for 7/6, but I deleted the existing login history for 7/6 and reran the plugin, and it wrote all of the rows correctly. However, I tried this for 6/17 (twice) and both times it failed at exactly the same place where it stopped writing the first time.

I have just discovered that some users have been incorrectly deactivated for inactivity due to this issue, so any help would be much appreciated.

date count(*) max(time)
2020-07-06 763 23:48:05
2020-07-05 75 23:55:53
2020-07-04 54 23:17:39
2020-07-03 314 23:41:08
2020-07-02 587 23:59:27
2020-07-01 142 10:15:13
2020-06-30 687 23:48:19
2020-06-29 523 15:20:02
2020-06-28 102 23:53:13
2020-06-27 88 23:45:35
2020-06-26 586 23:45:32
2020-06-25 694 23:46:02
2020-06-24 676 23:58:31
2020-06-23 557 19:02:40
2020-06-22 790 23:44:43
2020-06-21 77 23:48:33
2020-06-20 61 23:24:34
2020-06-19 642 23:51:23
2020-06-18 654 23:50:03
2020-06-17 72 07:50:31
2020-06-16 711 23:59:06
2020-06-15 705 23:37:09
2020-06-14 64 23:36:59
2020-06-13 57 23:37:49
2020-06-12 527 23:38:02
- Cancel
- Up 0 Down
- Reply
- More
- Cancel

Children

No Data