× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. January 2013

Re: Restrict User

Same thing I said, I think. The more ways we can say this, the better to understand, eh?

Vern

On 1/2/2013 4:31 PM, Graap, Kenneth wrote:
Ah, thanks - this gives the full explanation - #2 is not done when the user has no
*ALLOBJ on his own. #3 will be the thing that is found, when a private *EXCLUDE is
set on the object for that user. The group's *ALLOBJ is never checked.
Here is the way I understand this ....

#2 checks for *ALLOBJ special authority, if you don't have it, then checking continues on to step #3... If the object is set to *EXCLUDE for this user, then authority checking stops...and access is denied.

But if you give a user *ALLOBJ authority via a GROUP profile this allows you to modify a user's access to individual objects via private authority or authority list settings, before access is allowed via *ALLOBJ.

Reply or Forwarded mail from: Kenneth E Graap




As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.