Using nesting, you can add a group as a member of another group. You nest groups to consolidate member accounts and reduce replication traffic.
Nesting options depend on whether the domain functionality of your Windows Server 2003 domain is set to Windows 2000 native or Windows 2000 mixed.
By default, when you nest a group within another group, user rights are inherited. For example, if you make Group_1 a member of Group_2, users in Group_1 have the same permissions as the users in Group_2.
Linux: /opt/novell/nam/idp/webapps/nidp/WEB-INF/classes Windows Server 2008: \Program Files (x86)\Novell\Tomcat\webapps\nidp\WEB-INF\classes
Linux: /opt/novell/nam/idp/webapps/nidp/WEB-INF/web.xml Windows Server 2008: \Program Files (x86)\Novell\Tomcat\webapps\nidp\WEB-INF\web.xml
4.2 Add an entry for the ladpStorePlugins context parameter. Your entry should look similar to the following to associate the com.netiq.custom.LDAPStorePluginActiveDirExt with the Custom1 directory type.
<context-param> <param-name>ldapStorePlugins</param-name> <param-value>custom1:com.netiq.custom.LDAPStorePluginActiveDirExt</param-value> </context-param>
Linux: Enter one of the following commands: /etc/init.d/novell-idp restart rcnovell-idp restart Windows: Enter the following commands: net stop Tomcat7 net start Tomcat7
7.1 Click Access Manager > Identity Servers > Edit > Local.
7.2 Either select the name of a user store or click New.
7.3 For the Directory type, select the custom string you have configured above that is custom1
Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment. It just worked for at least one person, and perhaps it will be useful for you too. Be sure to test in a non-production environment.