Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Infor / Lawson Platforms
S3 Systems Administration
Iseries - Adopted Authority
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jessica
Past 24 Hours:
2
Prev. 24 Hours:
0
Overall:
5164
People Online:
Visitors:
201
Members:
0
Total:
201
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1348
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
S3 Systems Administration
Iseries - Adopted Authority
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
rhs
New Member
Posts: 4
10/14/2010 12:37 AM
We have just installed Lawson 9.0.1 on our iseries boxes. With Lawson 8 we were able to lock down our libraries/objects to *PUBLIC *EXCLUDE by ensuring adopted authority was setup correctly within all the Lawson libraries. Lawson actually had documentation to do this. Lawson is now saying that Adopted Authority is not possible in Lawson 9. Another consultant told me that the only way to lockdown to *PUBLIC *EXCLUDE would be to put "LAWSON" as a supplemental profile on all our individual user profiles. Has anyone done this? Any ideas on how to lockdown libraries and objects without putting "LAWSON" on everyone's profile?
Steven Gray
Advanced Member
Posts: 21
10/15/2010 4:08 PM
Are you running with UserProfiles for Lawson users set to GRPPRF *NONE?
rhs
New Member
Posts: 4
10/21/2010 9:34 AM
No. The user profiles each have a particular Group Profile that is not associated with Lawson. The LAWSON profile that we created for installation is not used as a Supplemental profile either.
Steven Gray
Advanced Member
Posts: 21
10/21/2010 12:26 PM
Try this
Data Library Object Authority OWNER=Lawson, *PUBLIC *USE
Data files Object Authority OWNER=Lawson, *PUBLIC *EXCLUDE
Lawson users UserProfile, GRPPRF *NONE, Suplimental Profile = *NONE
This worked OK when I tested it. Forms and reports ran OK. Printfiles, however, were owned by the user only. Usually they are owned by the user and Lawson.
This setup was suggested by a Lawson resource, and reported that it is working elsewhere.
If users need external access to any file, i.e queries or batch jobs, an Authority Group can be created and added to the file's authorization list, as needed.
You are not authorized to post a reply.