user password
Posted in 1998
Is there any mechanism available with ISQL's PERFORM language where I can enforce the constraint that a user must enter a password before a database record is added or updated? I have user login restrictions enforced by our Unix OS, table/form access controls that allow recognized users only to access a data entry form and this all works fine. However, if a user leaves his/her terminal open, logged onto the database server, with a data entry form accessed, then leaves their terminal unattended, ANYONE is able to make database record changes, add new records, etc. by using the unattended keyboard! I'm looking "downstream" at the US federal regulations on "electronic" signatures (21CFR part 11) since we may someday be required to comply and they require a second level of access (password, etc.) to assure reliance on an electronic signature for a record that requires a signature. Thanks for any thoughts, Jim -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=#=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Jim Kistler - kistler@an.hp.com # Some see issues and ask, "Why? Hewlett-Packard Co. Imaging Systems # Others see opportunities and 3000 Minuteman Road, Andover, MA 01810 # ask, "Why not?" TEL: 978-659-2251 - FAX: 978-687-7265 # -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=#=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-