This Object Class (inetOrgPerson) contains standard fields such as mail, uid. This value defaults to inetOrgPerson which is a standard object class defined in RFC 2798. If users can appear in organizational units within organizational units such as ou=development,ou=users,dc=sonatype,dc=com, this field should be True. For example, if all users are in ou=users,dc=sonatype,dc=com this field should be False. Values are True if there is a tree below the Base DN that can contain user entries and False if all users are contain within the specified Base DN. For example, if your users are all contained in ou=users,dc=sonatype,dc=com and you specified a Search Base of dc=sonatype,dc=com, you would use a value of ou=users. This DN is going to be relative to the Search Base, specified in Figure 8.2, “A Simple LDAP Connection and Authentication Setup”. The available fields are:Ĭorresponds to the Base DN containing user entries. The User Element Mapping displayed in Figure 8.4, “User Element Mapping” has been pre-populated by the Active Directory selection in the template drop-down and needs to be configured as required by your LDAP server. User and Group Templates Selection Drop Down
This panel provided a User & Group Templates drop-down displayed in Figure 8.3, “User and Group Templates Selection Drop Down” that will adjust the rest of the user interface based on your template selection.įigure 8.3. These configuration sections are located in a separate panel called User and Group Settings in Nexus Repository Manager Pro. The LDAP Configuration panel in Nexus Repository Manager OSS contains sections to manage User Element Mapping and Group Element Mapping in the User and Group Settings tab.