Login Information Parser

RE: Login Information Parser

yogeshd0002 — Thu, 16 Mar 2023 18:26:43 GMT

Hello,

Recently we started getting an error when trying to invoke the "Import Login Information" smart service. We are calling this smart service whenever user tries to login to the system first time, to capture first login details. We have not seen this error coming before, started from today itself.
It did worked for few users and thrown below error for couple of them so as such random behaviour

ERROR Message:
java.lang.NumberFormatException: For input string: "" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)

RE: Login Information Parser

spandanat — Thu, 30 Jul 2020 11:02:52 GMT

Hi[mention:0d1beecf844a473db6e88cb4a2b4fbc6:e9ed411860ed4f2ba0265705b8793d05],

Your server is configuration with 'High Availability' so we have 3 nodes of logs.

so we are missing data into table for around 445 users.

The Plugin is parse randomly available node, any solution for this?

RE: Login Information Parser

John Stretton — Tue, 07 Jul 2020 02:45:24 GMT

[mention:0d1beecf844a473db6e88cb4a2b4fbc6:e9ed411860ed4f2ba0265705b8793d05], 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

RE: Login Information Parser

Venkatesh Suram — Tue, 29 Oct 2019 11:41:35 GMT

Hi [mention:0d1beecf844a473db6e88cb4a2b4fbc6:e9ed411860ed4f2ba0265705b8793d05]

Hope your doing Well!

Observed the below issues with the plug-in.
1. When we pass the date as rule input to smart service but unfortunately if the log file is not exist on that date, the smart service is throwing the java.lang.NullPointerException. Is there any chance to handle in java code?.
2. The second one is which mentioned by [mention:9b313f6514bf4b6f98e31d2815bc2aad:e9ed411860ed4f2ba0265705b8793d05]

Can you please help out on this.
Thanks!!

RE: Login Information Parser

spandanat — Thu, 24 Oct 2019 11:16:37 GMT

Hi [mention:0d1beecf844a473db6e88cb4a2b4fbc6:e9ed411860ed4f2ba0265705b8793d05]

Hope your doing Well!

I could parse last one month files from system log named "login-audit.csv.2019-10-23" however the files before that were compressed and the named "login-audit.csv.2019-09-05.gz" and the plugin is throws null pointer exception.

can you update the plugin so that it should check for these extension file and if exist then it should be capable of extracting zip and read the file?
login-audit.csv.2019-09-05.gz>login-audit.csv.2019-09-05

Or do we have any other plugin which help me here?

Thanks in Advance

RE: Login Information Parser

Amitkumar — Mon, 17 Dec 2018 19:09:01 GMT

Has anyone used this plug-in with IBM DB2? Did it work successfully?

RE: Login Information Parser

erickp — Tue, 23 Oct 2018 18:54:04 GMT

Question: the login-audit.csv has information regarding the browser and device used to login. Does anyone know why this information was not added to the plugin to insert into the logins table?

RE: Login Information Parser

Eduardo Fuentes — Thu, 31 May 2018 19:36:34 GMT

Oh! good point. I was looking at a completely different plug-in. I apologize.

No, the existing version does not work with the shared logs functionality. It'll have to be updated in a similar fashion (similar to the code I posted above).

Components come with the source and are available to extension or modification from the participants of this community.

RE: Login Information Parser

Bala K — Tue, 29 May 2018 15:19:02 GMT

[mention:0d1beecf844a473db6e88cb4a2b4fbc6:e9ed411860ed4f2ba0265705b8793d05] I dont see the above code in the plugin src when i download it from App market. Is it updated version and available anywhere to download?

Below is what i see in com.appiancorp.loginparser-1.0.2.jar - com.appiancorp.loginparser.ImportLoginInformation.java

Code:

------------

String logsPath = ConfigurationLoader.getConfiguration().getAeLogs();

String dateString = "";

if(date != null){

DateFormat dateFormat = new SimpleDateFormat("yyyy-MM-dd");

dateString = "." + dateFormat.format(date);

}

LOG.debug("Reading file: " + logsPath + "/login-audit.csv" + dateString);

processLogins(logsPath + "/login-audit.csv" + dateString);

RE: Login Information Parser

Eduardo Fuentes — Tue, 22 May 2018 15:39:04 GMT

As explained in docs.appian.com/.../High_Availability_and_Distributed_Installations.html in an HA set-up the use of a shared-logs folder is the recommendation.

When you go to the logs of your cloud-site you should see that the logs are read from the shared-logs location.

Looking at the code it seems it is designed to look for files in there, which suggests it should work.

String logsPath = ConfigurationLoader.getConfiguration().getAeLogs();

String logParentPath = new File(logsPath).getParent();

String sharedLogsPath = logParentPath + File.separator + SHARED_LOGS_FOLDERNAME;

if (new File(sharedLogsPath).exists()) {

List<File> allSharedLoginAuditFiles = new ArrayList<>();

allSharedLoginAuditFiles = listf(sharedLogsPath);

if(allSharedLoginAuditFiles.size() > 0) {

for (File file : allSharedLoginAuditFiles) {

processLogins(file.getAbsolutePath());

}

I encourage you to review the login-audit.csv files in the logs folder (aka shared-logs for HA) and review whether it contains all logins, if so, then the plug-in will work because it will read it from shared-logs.

RE: Login Information Parser

vishalg — Wed, 16 May 2018 13:00:16 GMT

Hi [mention:0d1beecf844a473db6e88cb4a2b4fbc6:e9ed411860ed4f2ba0265705b8793d05]

We are currently on High Availability (HA) setup and want to get full picture of all the logins on the system.

I came across this plugin recently. I wonder if you know if this plugin caters for High Availability multi-instance setup where there may be 1 login-audit file per instance?

Thanks

Vishal

RE: Login Information Parser

Ben Dudley — Mon, 05 Feb 2018 22:41:16 GMT

Hi [mention:a52279d8b0cb4a6b8a2b233be546e7a8:e9ed411860ed4f2ba0265705b8793d05], [mention:0d1beecf844a473db6e88cb4a2b4fbc6:e9ed411860ed4f2ba0265705b8793d05] made an update to the Plug-in listing and the sample DDL for the table now references a length of 50. Thanks for the suggestion!

RE: Login Information Parser

bradc — Fri, 02 Feb 2018 18:01:32 GMT

To those using this plugin - I discovered an issue where some of our users are logging IP addresses longer than the 20 characters set on the table in the documentation. The IP address logged is two addresses separated by a comma and space. I would recommend extending the ipaddress column length to at least 50 (I did 100 just to be safe) to avoid this issue. The plugin will simply write records up to the point a record would be truncated and stop writing additional records.

Here is a link to some information I found regarding why there would be two IP addresses logged:

serverfault.com/.../742754