Kbase P112132: Applying Dynamics security with All Groups applies changes to the Admin user.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
07/11/2007 |
|
Status: Unverified
FACT(s) (Environment):
Dynamics
Windows
Progress 9.x
OpenEdge 10.x
Dynamics
SYMPTOM(s):
Applying Dynamics security with All Groups applies changes to the Admin user.
Dynamics All Groups security applies security to users that are not in any groups, like the Admin user.
CAUSE:
Users that do not appear to be defined in any particular group are members of the Default Security Group. Dynamics "All Groups" security also applies to the Default Security Group.
FIX:
Applying changes to All Groups does apply to the Admin user, but this is because the Admin user is a member of the Default Security Group. You can create your own Default Security Group, but if you have not done so there is one created for you by default with Security Maintenance when you add security structure records. So although the Admin user does not appear to be in a group, he actually is in one.
If you do not want the admin user to be subject to changes by "All Groups", then you have 2 choices:
1. Separate "normal" users and Admin users into two separate groups and do not use "All Groups".
2. For every security structure you apply with "All Groups" create exactly the same structure record specifically for the Admin user, but with "Full Access". Since Dynamics applies security that is specific to users before groups, Dynamics will apply the Admin user specific structure record and not the group specific structure record.