The obvious (to me... YMMV) solution would be to have a process run out of the login paragraph which requires a username and password which could be stored in a file with an @id of their @userno. A second process which parses the output of a LISTU command and shows the current username assigned to a given @userno would tell you who is logged in from the java app at any time. If you wanted to get a bit more involved you could even check the IP address of the user and only require a secondary username/password for those coming from your firewall
[EMAIL PROTECTED] wrote: [stuff snipped] > >The challenge I have is to figure out who/what is logging in when they are >using a java telnet client we use for 'web-based' connectivity. The >functionality of it is, briefly, an HTTP connection to our web server, >which downloads a java telnet app to their PC, which initializes a telnet >connection through our firewall to our uniVerse server. Because of that, >when we do a listu/who -u we get our own domain.com as the answer (AIX >5.2/UV 10.1.7). Jeff Schasny | Denver, Colorado, USA | [EMAIL PROTECTED] ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
