12.3 Set Corporate Redirection

Corporate redirection functionality bypasses native directory inheritance by specifying, in the Corporate redirection tab of the Advance Settings pane, the object from which the object will inherit its SecureLogin configuration. Although inheritance is “redirected” to a specific object, such as a container or organizational unit, local user object settings continue to override the inherited settings.

Inheritance of SecureLogin data using Corporate redirection functionality stops at the container/organizational unit. Any settings, enabled applications, or password rules that are inherited by the container or organizational unit providing the SecureLogin environment will not be inherited from a higher level directory object.

In the following example, the Finance organizational unit is redirected to inherit the SecureLogin configuration from the Development organizational unit.

  1. Access the Administrative Management Utility of SecureLogin.

    For more information on how to access the Administrative Management Utility see, Section 1.2, Administrative Management Utility and Section 1.3, Accessing the SSO Plug-In Through iManager.

  2. Click Advanced Settings. The Advanced Settings pane is displayed.

    Advanced settings pane

  3. Specify the full distinguished name of the object in the Corporate redirection field.

    NOTE:The full distinguished name is required to uniquely identify the container or organizational unit.

  4. Press the Apply.

  5. Click OK.

    IMPORTANT:Ensure that you do not overwrite administrator settings when distributing SecureLogin configuration environments. For example, if you set the preference Allow users to view and change settings to No and then copy this as part of a SecureLogin environment to the container/organizational unit, including the Administrator user object, the administrator cannot view or change SecureLogin settings since they reside in that organizational unit. To prevent this from happening, it is recommended that all administrator user objects are located in a separate organizational unit, and administrator preferences are manually configured.