Can we use compat tree for AIX? This seems like a less intrusive solution.

Yes, that is a good alternative. It is probably more correct to use automountKey as the RDN but at this point we may not have a lot of choice.

May be CoS can help?

Changing 3.2 priority

Moving to milestone dedicated to Cross-Distro support. We would like community members (especially AIX users) to contribute the fix.

Looks like this is more difficult than originally thought. The key entry is a child of the map entry and this type of relationship is not supported in the compat plugin. The only way to do this today is to create a separate key configuration for each map. One compat plugin will support all maps (for a given location).

Locations throws another wrench in the mix because then the maps and locations have the same parent/child relationship. So one would end up with a whole lot of compat entries.

Here is the map configuration for the default location:

dn: cn=automountmap, cn=Schema Compatibility, cn=plugins, cn=config
default:objectClass: top
default:objectClass: extensibleObject
default:cn: automountmap
default:schema-compat-container-group: cn=compat, $SUFFIX
default:schema-compat-container-rdn: cn=automount
default:schema-compat-search-base: cn=default, cn=automount, $SUFFIX
default:schema-compat-search-filter: (objectclass=automountMap)
default:schema-compat-entry-rdn: automountmapname=%{automountmapname}
default:schema-compat-entry-attribute: objectclass=automountMap

Here is the map configuration for an automount map named auto.test:

dn: cn=auto.test, cn=Schema Compatibility, cn=plugins, cn=config
default:objectClass: top
default:objectClass: extensibleObject
default:cn: auto.test
default:schema-compat-container-group: cn=automount, cn=compat, $SUFFIX
default:schema-compat-container-rdn: automountmapname=auto.test
default:schema-compat-search-base: automountmapname=auto.test, cn=default, cn=automount, $SUFFIX
default:schema-compat-search-filter: (objectclass=automount)
default:schema-compat-entry-rdn: automountKey=%{automountKey}
default:schema-compat-entry-attribute: objectclass=automount
default:schema-compat-entry-attribute: automountinformation=%{automountInformation}
default:schema-compat-entry-attribute: description=%{description}

I don't know that this would provide any relief from the original work-around of manually creating key entries using automountKey as the RDN to mirror the IPA-generated ones.

linked upstream freeipa ticket 3029 to RH bz 1237346 for RHEL 6.6 report

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1237346 (Red Hat Enterprise Linux 6)