Are there any best practices for enforcing any kind of automatic timeout for logins? Also, what is the recommended way of seeing how long any given userid has been logged into the system without logging out?
I've tried writing some preliminary code that references both T_METUSER and TX_MACHINE_LOCATION, but they don't seem to be quite what I'm looking for.
Matt -
Are you needing something more than APPLICATION_TIMEOUT in the T_DEFAULT table?
The number of seconds of no activity (keystrokes, mouse clicks or mouse movement) before a warning message will appear, with an audible alert, indicating that the application will automatically close. For PCI compliance this must be set to 900 (15 minutes) or the Windows screen must be set to lock if the terminal is idle for 15 minutes. This setting can be overridden by an entry in the [Defaults] section of the local .ini file.
I'm assuming you probably are, but thought I'd ask in case it was an easy answer!
- Heather
Matt, you can build your procedure based on a Tessitura user's database process ID, by:
select spid FROM master..sysprocesses sys_WHERE dbid=db_id('IMPRESARIO')AND program_name LIKE 'Tessitura(%' --e.g.: Tessitura(ug=XXXX) and sys_.loginame = ... --from t_metuser.userid
then you can kill the process (be careful doing that) by :
USE masterKill <spid>
As example of a script which handles Tessitura user logins please find my procedure lp_chc_Repair_Tessitura_Login, attached.
Simon Basyuk, DBA at Carnegie Hallsbasyuk@carnegiehall.org