[MRM-1923] Fixing bind issue with certain ldap servers, when user not found

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.1
• Fix Version/s: 2.2.3
• Component/s: redback
• Assignee: Olivier Lamy
• Reporter: Olivier Lamy
• Created: 13/Sep/16 00:57
• Updated: 05/May/17 11:01
• Resolved: 13/Sep/16 00:58

Description

I had a issue in certain environments where subsequent calls of NamingResult#hasMoreElements returns different values.
e.g. it occured on IBM JDK 7 with Windows Active Directory LDAP when the first value of 'hasMoreElements' was false.
The first value is cached now.

Issue Links

• links to: GitHub Pull Request #10