Why does the automountd fail to resolve entries from LDAP using uppercase letters in their cn? (Doc ID 1343714.1)

Last updated on JULY 29, 2016

Applies to:

Solaris Operating System - Version 8.0 to 11.2 [Release 8.0 to 11.0]
Information in this document applies to any platform.

Goal

If a LDAP client is configured to use objectClass and attributeMapping for automounter data in LDAP,
where the /var/ldap/ldap_client_file contains...

NS_LDAP_ATTRIBUTEMAP= automount:automountInformation=nisMapEntry
NS_LDAP_ATTRIBUTEMAP= automount:automountMapName=nisMapName
NS_LDAP_ATTRIBUTEMAP= automount:automountKey=cn
NS_LDAP_OBJECTCLASSMAP= automount:automount=nisObject
NS_LDAP_OBJECTCLASSMAP= automount:automountMap=nisMap


... , then the automountd daemon will fail to find LDAP entries that contain uppercase letters in the value
of their cn attribute.

This document is intended to explain how the automountd behaves in that configuration, why it behaves
like that, and how a solution can become implemented.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms