Details
-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
2.5.42
-
None
Description
In a LdapToSqlSyncDaemon setup, the description for a translation field reads:
Enter a translation if there is no ldap attribute or if it needs to be adjusted. ldapAttribute_<attributename> (attribute name is lower case). All attributes and extraAttributes can be used. loaderLdapElUtils can be used, and ldapLookup. e.g. ${ldapAttributelastname + ', ' + ldapAttribute_firstname}. Mutually exclusive with 'LDAP attribute name'.
But I don't see anywhere in the source code for the class where loaderLdapElUtils and ldapLookup are added to the EL variable map. If I debug, I only see ldapAttribute__XXX variables.
Also, the text about "Mutually exclusive with 'LDAP attribute name'" is confusing. The LDAP attribute name field doesn't show up when doing a translation, so it's not something users need to worry about.
It does work with the full path to the LoaderLdapElUtils class, since it's a static method. So this works:
${edu.internet2.middleware.grouper.app.loader.ldap.LoaderLdapElUtils.convertDnToSpecificValue(ldapAttribute__XXX)}
|
When changing the description text, it may also be useful to note that the virtual attribute EntryDn should be available as an attribute name, and ldapAttribute__EntryDn for a translation. This is due to the Dn handler added by default to the LDAP settings.