Row Security

rfletche

Active Member
Hi!
We're at B7332 SP14. We would like to use *PUBLIC Row Security to close
access to all users and then give specific users/groups explict ranges,
e.g. Cost Center Range of 0028 to 0028. Unfortunately, it appears that
the user can also see other Cost Centers and that Row Security only sees

the first selection, 0028 to 0028 and ignores the *PUBLIC default.
Does this happen to anyone else?
regards
Alexander and Robert
 
This is the way that row security works, it set row security at a higher level then any row security defined lower such as group and *PUBLIC is ignored. So when defining row security I normally set it a user level if the users have got all different branch plant access etc.

In essence, you must completely define your row security at one level, which level is what you decide depending on the complexity.

Simon


On Thu, 03 May 2001, rfletche wrote:
 
Hello Alexander & Robbert,

What Simon means is that *PUBLIC only works if the user is NOT a member of =
a group. Group security overrides *Public . So even when there is no =
security set up for a group the *Public settings are ignored. The same =
applies to user specific security.If user specific security is entered the =
group settings are ignored completely.

In essence combined with the inability to be a member of multiple groups =
(such as in NT) setting up security in OneWorld is a drag.
=20
Best regards,


Walter Brink



Hi!
We're at B7332 SP14. We would like to use *PUBLIC Row Security to close
access to all users and then give specific users/groups explict ranges,
e.g. Cost Center Range of 0028 to 0028. Unfortunately, it appears that
the user can also see other Cost Centers and that Row Security only sees

the first selection, 0028 to 0028 and ignores the *PUBLIC default.
Does this happen to anyone else?
regards
Alexander and Robert






--------------------------


OneWorld Xe
Unix HP9000 11
Oracle 8.1.6
 
I believe you would need to set on row security in data dictionary also for
MCU.

If you don't want them to use the visual assist at all, you could secure the
users from using the application behind this visual assist, which I believe
is P0006S. Might be less of a performance hit.




Xe, SP 17.1_E1, Update 2, ES=AS/400 V5R1, CO=AS/400, Thick & Citrix Clients
 
Back
Top