Thanks for your input, Tony. I almost always find your responses to the
list to be thought-provoking.
I think for this project (converting greenbar reports to screen or exports)
I'm going to go with the "hard way" approach. The "easy way" is
interesting, but much more complex to set up than the "hard way". I'm not
even certain that Viaduct supports login scripting. It probably does, but
I've not looked at it for much beyond data import/export scripting.
If I understand how the "easy way" would work, the user would ask for a new
connection/login from the emulator. In response, the emulator runs a
script, prompting for userid, password, then passing it to the server. Once
the user is logged in, the emulator's script would be able to call it's own
specific "programX" which would store emulator type for that session. U2
would record the emulator type and then execute a logto into the regular
"MAIN" account, which would then execute it's own LOGIN script. The
emulator type would have to be stored under a unique id specific to that
user/port id and/or process id to allow for multiple logins.
Do people using login scripts with their emulators add auditing for changes
of the scripts on each PC to their internal security scans? It would seem
to be an ideal place for an unscrupulous someone to insert a password
capture routine. No, a better, more secure approach would be to put the
login script on the network, and have the emulator run the centralized (and
audited) script. How you lockdown the emulator settings to only use the
centralized script is another exercise.
Regards,
--bev
____________________________
Bev Wilson
410.309.2700 voice
410.309.2701 fax
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
