This content has been marked as final. Show 2 replies
1 of 1 people found this helpful
Hmm.... looks like yet another bizarre quirk of JNDI. What if you construct the name as an LdapName and call getAttributes with the LdapName instead of a string?
Thank you so much! Using LdapName worked.