We have an proprietary LDAP database that will not accept unescaped # or = in RDN values for in aliasedObjectName.
While that sounds non-RFC-conformant to me, it would be great if there would be an ability in ldapsdk to work around that by escaping those.
The legacy system used javax.naming.ldap.Rdn.escapeValue for that and thats in the end the exact behaviour we would like to replicate.