4GL users restriction level in PROGRESS RDBMS

progress_in

New Member
Hi,

I have Progress database running on version 10.2B02 with some SQL and 4GL users.

Do we have GRANT, REVOKE permission levels for 4GL users. Is there a way we can restrict some 4GL users by revoking there write permission.

Also would like to know more about Auditing... its benefits, issues etc
want to enable auditing in near future.

Thanks,
 
4gl users can have read & write permissions specified. But the mechanism is different -- it is done through "data administration".
 
Note that the simple facilities provided through data administration are rarely what one really wants for an application. I would suggest thinking about what you need in terms of security and access and creating an application module to deal with that using the client-principle object. Come to PUG Challenge Americas to learn how!
 
Are you talking about "data administration -> Security -> Edit Data Security... " option. This looks to be a table level restriction. Database i am working on have around 250 4GL table with around 150 odd users (each with unique user ID). Add/delete/modify permission USERS will be an on going activity.

If this is the only solution at "Database Level" for User level restriction, would like to know

a) If there is limit for the number of entries we can have in any of the VST table field like ( _file._can-write, _file._can-read )
b) would like to handle this through a automated script, modification of VST tables using automated script comes under good practices for DBA or not ??

Thanks,
 
I think you need to let go of the SQL view of a Progress database (GRANT permissions per user, per table). The permissions on tables of an application can be handled like this but, like tamhas said, it is in most cases better to deal with authorisation within the application. IMO authorisation should not be work for a dba-er but should be done by the users of the application.
 
Back
Top