ALLOBJ

[Maynor]

Does my users need allobj auth, to be able to run JDE?

 

[Dave Kahn...]

No. It should be sufficient that your users are members of the JDE
group. The JDE profile should not need *ALLOBJ, but it should be the
owner of all JDE objects. Thus your users have unrestricted access to
JDE objects as far as operating system security is concerned. Menu,
business unit, action code, and search type securities are then meant
to control what your users can do within JDE. This is not ideal but it
is the standard JDE approach. It's fine as long as your users cannot
access JDE objects from outside JDE, and it's much better than
granting them *ALLOBJ which would open up non-JDE objects to them as
well.

 

[G_Smith]

No, Never, and I can't think of enough other ways to say no.

Each shop has determined their own needs for security and we have each user at a Class = *USER, Special Authority = *JOBCTL, and Group Profile = JDE. There is some discussion as to the Special Authority of JOBCTL but I believe it is a carry over from earlier releases of JDE World Software.