User installed SecureLogin in ADS mode and everything appeared to be OK. After a while, problems occurred which appeared to be related to rights. Upon further diagnosis it was discovered that some AD rights werenât inherited by some Users. Users require rights to read SSO configuration information such as which applications are SSO enabled, and write (save and encrypt) information such as their application usernames and passwords to the directory.
When they were set directly on the User objects, after one hour passed these rights assignments automatically reverted to their old/default values.
These operator groups are ""protected"" - groups. When users are or were in protected groups the attribute admincount is set to ""1"". This user will not be able to inherit the settings from the OU.
Using the ADSIEDIT.MSC you can solve this issue when you go to the objectproperties of the user. Youâll find in the attributes, ""admincount = 1"".
When you set this value to ""0"" the user will inherit all settings from the organizational unit, including SecureLogin SSO.
By setting this value to ""0"", the userâs group membership to the âoldâ protected groups, account-operators and print-operators, is effectively removed (even if the user is still member of the actual group)
For more information, please refer to the MS KB article below:
Microsoft announced this behavior may occur when you update your existing Windows NT or 2000 domain controller to a Windows Server 2003 DC.
These three issues occur:
- Delegated permissions are not available to all users in an organizational unit.
- Inheritance is automatically disabled on some user accounts approximately one time an hour
- Users who previously had delegated permissions, no longer have them.
This problem may also occur after you apply the hotfix 327825 to Microsoft Windows 2000 Server or after you install Windows 2000 Service Pack 4 on a Microsoft Windows 2000 Server.