With the introduction of the eDirectory group membership feature in the SecureLogin 6.1 release, you must make additional attribute assignments to the group objects. This is primarily required when users are using different administrative management utilities such as NWAdmin, ConsoleOne, or iManager.
Launch the Administrative Management utility (iManager, or SLManager).
Specify the distinguished name of the container object you want to modify.
NOTE:SecureLogin only supports configuring group memberships within a container object.
Select Advanced Settings > Configured Groups. The Group Configuration dialog box is displayed.
Click Add. The Adding a group dialog is displayed.
The list shows the group objects configured in the current object.
Provide the distinguished name of the group object.
Click OK to add the new group object. The Group Configuration dialog is displayed.
Use the Up and Down options to promote or demote the order in which the group policies are applied.
NOTE:Within the Group Configuration, the higher group takes precedence.
Configured groups can only be set against containers like O and OU and not set against a user object. In such a case, contrary to the earlier statement, the higher container takes the lower precedence.
After you have configured single sign-on settings for a Group, the configuration is not reflected in iManager when looking at the SecureLogin information for any of the assigned group members. For example, the group “Everyone” might contain a single application called “innerweb”.
When looking at the defined SecureLogin applications from within the properties of a group member, you will not see the "innerweb" application listed. However, the configured application will be available in the client when SecureLogin is launched at the workstation.