SecureLogin Corp Redirection and Configured Groups

  • 7004014
  • 29-Jul-2009
  • 26-Apr-2012

Environment

Novell SecureLogin
NSL6.1

Situation

Corporate redirection has long been an option for configuring applications and settings for SecureLogin.  Through corporate redirection a container can be pointed to another container from which SecureLogin applications and settings will be read. This allows the administrator to configure SecureLogin on a single container, and to point all other containers to that one source from which to read their SecureLogin settings.

Beginning with NSL 6.1, SecureLogin also has the option to configure applications and settings on group objects as well as on container or user objects.

Questions:
1. Do settings configured on the group or settings configured on the container take precidence? 
2. Do settings configured on the group or settings configured through corporate redirection take precedence? 
3. If  a group is added to a container's "group list" will settingsconfigured through corporate redirection apply to the group?



Resolution

Answers:
1. Settings made on the group object take priority over settings made on  a container. 
2. Settings made on the group object take priority over settings made though corporate redirection. 
3.  Settings configured through corporate redirection will not apply to group listed in the containers configured groups list.

The idea of configuring SecureLogin on Groups was devised to allow users across multiple containers to share settings, and to overwrite configuration settings made on a container.  The regular eDirectory inheritance applies; namely settings made on users supercedes  settings made on groups which supercede settings made on a container.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.