HP3000-L Archives

October 1997, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jim Phillips <[log in to unmask]>
Reply To:
Jim Phillips <[log in to unmask]>
Date:
Thu, 30 Oct 1997 10:59:49 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (23 lines)
Michele:

I don't know of any product that can enforce application security at 
the transaction level (and that seems to be what you are looking for) 
as an add-on to your home-grown application.

Since you have the source for the application, it would make sense 
to add transaction level security to the application yourself.  That 
is what we have done with our system.  Each screen is identified by a 
transaction code and we maintain a data base record for each transaction 
that spells out what each user can do with that transaction (add/change/
delete/inquire).  Of course, our system was designed with this idea 
in mind from the very beginning.  You may have problems in adding this 
feature after the fact.

If you would like more details in how we do this, please feel free to 
contact me directly.

Jim Phillips                            Manager of Information Systems
E-Mail: [log in to unmask]      Therm-O-Link, Inc.
Phone: (330) 527-2124                   P. O. Box 285
  Fax: (330) 527-2123                   Garrettsville, Ohio  44231

ATOM RSS1 RSS2