Author Topic: Last Login Time for supervisor CME users  (Read 726 times)

Offline hsujdik

  • Sr. Member
  • ****
  • Posts: 258
  • Karma: 13
    • Genesys Brasil
Re: Last Login Time for supervisor CME users
« Reply #15 on: August 09, 2018, 05:57:16 AM »
There is another option for historical reporting that I just thought about (the problem is solved already, but just for a matter of keeping it recorded here):

You could create a Database Trigger that runs after UPDATEs on the table CFG_HDB_LAST_LOGIN and save the data of the new values on a customized table. That way, you can record each login of a person, and have control of the retention rules.

Offline zwerg82

  • Newbie
  • *
  • Posts: 22
  • Karma: 2
Re: Last Login Time for supervisor CME users
« Reply #16 on: August 09, 2018, 02:18:15 PM »
I thought of triggers too, but if you have both solutions enabled, you have:

1. all logins in log db, and you can configure how long you want to store those by defining it in your purge job (cat 2, prio 2)

2. in config db you have the actual last login for every user, which helps to identify „dead“ accounts.

Wouldn’t it make more sense to do the trigger on log db? Especially because it gives you the ip?



Online Kubig

  • Hero Member
  • *****
  • Posts: 2481
  • Karma: 41
Re: Last Login Time for supervisor CME users
« Reply #17 on: August 09, 2018, 07:37:04 PM »
I am not sure about the table CFG_HDB_LAST_LOGIN  whether contains all attempts to log into Genesys environment as I saw a few installation where this table was always empty (even the HDB was enabled). So I would not rely on it
Genesys certified professional consultant (GVP, SIP, GIR and Troubleshooting)

Offline zwerg82

  • Newbie
  • *
  • Posts: 22
  • Karma: 2
Re: Last Login Time for supervisor CME users
« Reply #18 on: August 09, 2018, 08:17:03 PM »
At least for me it's tracking all logins for now in a test environment.
If the customers are using CSProxies they have to be configured to sync this information with confserv.

I have to admit , that I like the solution via log db more.

Offline hsujdik

  • Sr. Member
  • ****
  • Posts: 258
  • Karma: 13
    • Genesys Brasil
Re: Last Login Time for supervisor CME users
« Reply #19 on: August 10, 2018, 03:55:27 AM »
At least for me it's tracking all logins for now in a test environment.
If the customers are using CSProxies they have to be configured to sync this information with confserv.

I have to admit , that I like the solution via log db more.

Just an additional info for that solution, then:

The Log DB does not automatically purge by default. The administrator is reposible for either run the Log DB Maintenance Wizard or create an automated job for purging old data.
In that case, it is interesting to include a "WHERE" clause in order not to delete the records which have the messageid = 22121 or else this historical report would be compromised


Edit: I just realized you have already added that note :)