× 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.



I have a user owned by GRP_SD with the following profile parameters:

User class . . . . . . . . . . . . . . . . : *USER

Group profile . . . . . . . . . . . . . . : GRP_ROA
Owner . . . . . . . . . . . . . . . . . . : *GRPPRF

The user can see MOST user profiles owned by GRP_ROA but not all with the wrkusrprf command. The user can see one user profile owned by GRP_SD with the user class set to *USER and group profile set to *NONE and no other GRP_SD owned profiles.

The user claims that she could see all profiles owned by GRP_SD before we upgraded to V7R1. I created a copy of this profile for testing purposes so there are no authorization lists or anything special involved. Has V7R1 closed some type of loophole? Why would one profile owned by GRP_SD be visible while the others are not? When I added GRP_SD as a supplemental group in the profile all GRP_SD owned profiles were visible. Again this made sense so I'm not sure how it worked before.

I haven't had to do this much security research in quite some time and I may have missed something that changed in V7R1. Hopefully someone can point me in the right direction. I considered opening an IBM ticket, but I'm just not sure it is their problem.

Becky Bakutis
Systems Engineer
Republic Services

480.627.2760 (w)
bbakutis@xxxxxxxxxxxxxxxxxxxx


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.