SecureLogin preferences, application definitions, password rules, and credentials are collectively the SecureLogin configured user environment. You can deploy and maintain this environment at all object levels, including import/export by file, copy to another object, and so forth. The SecureLogin data can be added to users, containers, groups and even through Group Policy Objects in Active Directory environments.
A single sign-on environment that is configured at the container, organizational unit, or Group Policy level is inherited by all associated directory objects in the hierarchy.
First, enable applications for single sign-on with one user, then copy the applications to the container, OU or Group Policy level for mass deployment. This applies to all SecureLogin configurations, including password policies and preferences. Lower-level settings that you manually configure always override higher-level settings. Therefore, configuration at the user object level overrides all higher level configuration settings. You can manually disable inheritance from objects higher in directory by selecting Yes next to Stop walking here in the Preferences of the desired object. For example you can set this value at the partition boundaries to keep users from needing to walking across WAN links to locate inherited values for SecureLogin.
The inherited settings include configuration properties, application definitions, password policies, and credentials. For example, if a user belongs to the following hierarchy of containers and groups:
Container 1: SettingsOfContainer1
Container 2: SettingsOfContainer2
Group 1 applies to Container 2: SettingsOfGroup1
User: settings, credentials
Then, the user will inherit SettingsOfContainer1, SettingsOfContainer2, SettingsOfGroup1, settings, and credentials. However, the preference values set at the user object level override any values inherited from other objects in the directory. The settings configured at the lower level in the hierarchy take precedence over the settings at the higher level. For example, settings in container 2 would take precedence over settings in container 1.