-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 6.0.0.4
-
Component/s: trees
-
Labels:
-
Target Version/s:
-
Rank:1|hzpuf3:
-
Sprint:AM Sustaining Sprint 55, AM Sustaining Sprint 56
-
Story Points:3
-
Needs backport:Yes
-
Support Ticket IDs:
-
Needs QA verification:No
-
Functional tests:No
-
Are the reproduction steps defined?:Yes and I used the same an in the description
Bug description
Same bug as OPENAM-13530, but with LDAP Decision Node
How to reproduce the issue
Same as with OPENAM-13530 but create a tree with a LDAP Decision node
Expected behaviour
The shared state before and after failing to authN contains the username
Current behaviour
amAuth:09/06/2018 01:37:36:253 PM BST: <SKIP> Connecting to [http://opendj.example.com:1389] Searching dc=example,dc=com for (uid=demo) scope = sub amAuth:09/06/2018 01:37:36:253 PM BST: <SKIP> userAttrSize is : 1 amAuth:09/06/2018 01:37:36:261 PM BST: <SKIP> Cannot find entries for (uid=demo) amAuth:09/06/2018 01:37:36:261 PM BST: <SKIP> loginState userNotFound amAuth:09/06/2018 01:37:36:261 PM BST: <SKIP> newSharedState {realm=/, authLevel=0}
Code analysis
LdapDecisionNode.java
case USER_NOT_FOUND:
newState.remove(USERNAME);
- caused
-
OPENAM-14080 LDAP Decision Node returns incorrect user attribute to search for in user store
-
- Resolved
-
- is related to
-
OPENAM-13530 Datastore Decision node removes username from shared state when it is not found
-
- Resolved
-
- relates to
-
OPENAM-13530 Datastore Decision node removes username from shared state when it is not found
-
- Resolved
-