Hi Graham,
Typically when I set up security I do it during the CRP phase of an
implementation so that it can be tested by the core team and fine tuned
before go live.
Also I've found it best to have security in place during testing so that
the end-users do not see lots of stuff during training and then feel
targeted when they get only a few menus at go-live although your appl.
consultants may feel differently.
During CRP you should set up the user groups that you will need and grant
them the appropriate security so that they can do their jobs.
Grant JDE and any admins you have Appl=*all Security= *all so they can get
into anything.
When you feel that you have the correct security in place for your groups
you can turn Security OFF for *Public. This is actually less time
consuming. Think about it. If you have 20 programs across 6 modules and
you want a user to have just one module... is it easier to grant them
access to one module? Or to deny them access to 5? There are less security
records when you grant groups what they need and turn *public off. Also,
less security records means faster menu navigation and performance in that
respect.
Beware! When you turn off *Public security there are certain things
that need to be turned back on... such as Printer Selection, Password
change capability, UBE selection, Version Selection, etc... otherwise
people can get into their application but none of the basic system
functions like selecting Versions and submitting jobs. I have a list of
about 76 programs that I give access back to *Public for. It's fairly
complete but with each new release I find more.
I hope this helps.
Regards,
Gerald.
Graham.Aberdein@c
larica.com To:
[email protected]
Sent by: cc:
owner-jdelistml@j Subject: OW Xe Security - *PUBLIC (ON or OFF)?
delist.com
08/24/2001 12:15
AM
Please respond to
jdelist
Hi List,
I know this is not a black or white question, but we are
implementing OWXe
and would like to hear from others on whether they turn
*PUBLIC on or off.
We have generally heard/been told that *PUBLIC turned ON
is less security
setup work/more risk and *PUBLIC turned OFF is more
security setup
work/less risk. What we're struggling with is
quantifying both the
workeffort and the risk.
Thanks in advance for your help.
Graham
--------------------------