Log baan access

günther · #1 9th December 2015, 16:38

Hi,

does anybody know a way to write log entry (e.g. to a file), when a user logged in into Baan?

We (IT department) are regulary tested and have to proove that the user account has been disabled/deleted if the user leaves the company etc.

Regards
Günther

RedBatz · #2 9th December 2015, 19:33

Hi,

In ttaad2100m000 there is a History option (ttaad200.hist).

Checking this option for a user will log at {$BSE}\lib\TIME.HIS the sessions executed by the user, and the main menu object ottdskmbrowse (executed at login).

Hope it helps.

NPRao · #3 10th December 2015, 15:51

Quote:

does anybody know a way to write log entry (e.g. to a file), when a user logged in into Baan?

If you are HPUX, you can use the last command -

Quote:

LAST,LASTB(1) Linux System Administrator’s Manual LAST,LASTB(1)

NAME
last, lastb - show listing of last logged in users

SYNOPSIS
last [-R] [-num] [ -n num ] [-adFiowx] [ -f file ] [ -t YYYYMMDDHHMMSS ] [name...] [tty...]
lastb [-R] [-num] [ -n num ] [ -f file ] [-adFiowx] [name...] [tty...]

DESCRIPTION
Last searches back through the file /var/log/wtmp (or the file designated by the -f flag) and displays a list of all users logged in
(and out) since that file was created. Names of users and tty’s can be given, in which case last will show only those entries matching
the arguments. Names of ttys can be abbreviated, thus last 0 is the same as last tty0.

Quote:

We (IT department) are regulary tested and have to proove that the user account has been disabled/deleted if the user leaves the company etc.

You can query the /etc/passwd and the /etc/shadow files for the info.

Quote:

In ttaad2100m000 there is a History option (ttaad200.hist).

This option also work IF you enabled the History in the User Data Template and also that you have not purged the TIME.HIS file

günther · #4 14th December 2015, 09:05

Thanks a lot for the replies.

@RedBatz: I'm a bit scared about the heavy logging that will cause. We have nearly 700 users, and each session start will create a log entry to that file.

@NPRao: We're on unix, but I cannot use last, because our users are using the GUI and therefor there is no unix login.

At the moment, we have a glue script that is called before bshell gets started and that works fine for 99,9% but the 0,1% give 100% of work, discussion and so on. The Problem is, that we do not log "when a user logged in" but "when a user >>tried<< to log in".

Any other ideas?

Regards
Günther

shah_bs · #5 14th December 2015, 21:15

'last' will work, because even with GUI, there is still 'under the hood' unix connection required. You can check by running the last command for a user whom you know is no longer using BAAN (hopefully you have yet to take action to remove his access.)

Although, it will take some shell programming to get only the one record that is interesting. 'last' command gives all instances of when the user last logged in, assuming that the 'last' 'database' has not been cleaned up.

günther · #6 15th December 2015, 07:40

Funny. We're also on HPUX, but I cannot get that working. A user which is now running Baan is not displayed by 'last <unix-login>'; our /var/adm/wtmps is beeing regularly archived which can be seen by the line "WTMPS_FILE begins at Tue Dec 15 04:00:02" - but now it's 6:39 and the user has logged in 6:37.

Regards
Günther

günther · #7 15th December 2015, 07:46

Meanwhile, I raised an incident at Infor and got called back. I was told that I'm not the first one to ask about that. After some technical discussion we came to a simple solution: Write a small 3GL script that does the logging (to file(s) or database, one record per user or per user and day or ...), create a session for that and create a startup session group that uses this session; link all uses to that startup group (ttaad2105m000).

I've already tested that and it Looks fine!

Regards
Günther

Shyamb · #8 25th November 2022, 12:34

As mentioned we had collected the baan application last login file from /var/log/wtmp but here the challenge is that it contains all the history of user logins and our requirement is that to pull the data of last login with respect to each baan user and rest login dates should be skipped with respect to that user.

is there any way out to tackle this requirement?

Note: - we do not need last login details from OS level

günther · #9 25th November 2022, 12:49

Hi.

Funny, it's a real old thread. Meanwhile, I have a straight-forward solution for Baan IV:

1. Create a Baan IV Session, e.g. <xx><yyy>login. Program Script as a 3-GL, that tracks the login user, date and time to a new table.
2. Create a Session Group "login" in ttaad2107m000.
3. Add the Session <xx><yyy>login to the Session Group "login" in ttaad2106m000 (+ Convert to Runtime).
4. And if you're on Unix: The name of the B-Shell must be "bshell" not "bshell6.1"; so I created a symbolic link from $BSE/bin/bshell6.1 to $BSE/bin/bshell. Otherwise the Startup-functionality will not work!
5. If that all works, you can create Display/Print Session "onyl the last login", "all logins" and so on.

Regards Günther

OmeLuuk · #10 6th December 2022, 20:31

And all this could have been solved with some ksh scripting as well, since the "bshell program" is also possible to refer to a script calling actual bshell6.2 but after logging was written. And loging of the end-exit bshell as well... done that back in the day...

günther · #11 7th December 2022, 07:18

Are you sure, that this approach logs the successful login, or does it log the try to login? That was our initial problem.

Regards
Günther

OmeLuuk · #12 7th December 2022, 11:14

Ah there you have a point, but when logging just before bshell starts and after bshell ends you will know the time spent so also failed logins are logged, but with a very short time span.

Henk Spanhaak · #13 3rd January 2023, 16:44

We made a 3-GL script to add a record in an own table with the user and the current date. We created a BMS mask for this, session ttadv4188m000, both options to add mask and boot on yes. This 3-GL script will be started when the bshell is started and a record will be written in the own table.