Bug 1288668 - [GSS](6.4.z) The root cause of login module failures gets lost when multiple login modules are stacked
Summary: [GSS](6.4.z) The root cause of login module failures gets lost when multiple ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Security
Version: 6.4.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.12
Assignee: Tomas Hofman
QA Contact: Josef Cacek
URL:
Whiteboard:
Depends On:
Blocks: 1274287 eap6412-payload 1375727
TreeView+ depends on / blocked
 
Reported: 2015-12-04 23:09 UTC by dhorton
Modified: 2019-09-12 09:29 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-01-17 13:12:06 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-2817 0 Major Verified [GSS](7.0.z) The root cause of login module failures gets lost when multiple login modules are stacked 2017-08-04 11:50:48 UTC
Red Hat Issue Tracker JBEAP-5343 0 Major Verified (7.1.0) The root cause of login module failures gets lost when multiple login modules are stacked 2017-08-04 11:50:48 UTC

Description dhorton 2015-12-04 23:09:26 UTC 
Description of problem:
The root cause of login module failures gets lost when multiple login modules are stacked and the "flag" attribute is set to "optional".

When the login attempt fails (invalid bindCredential on the LdapExtLoginModule for example) the authentication request will continue to the next login module in the stack.  In this situation, the exceptions "cause" attribute is getting overwritten during the processing of the other login modules.  This results in the actual cause to get lost during processing.

This makes troubleshooting authentication failures difficult.
Comment 7 Mike McCune 2016-03-28 23:39:55 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 8 JBoss JIRA Server 2016-05-23 08:04:43 UTC 
Tomas Hofman <thofman> updated the status of jira JBEAP-2817 to Coding In Progress
Comment 10 JBoss JIRA Server 2016-08-02 08:09:34 UTC 
Bartosz Baranowski <bbaranow> updated the status of jira JBEAP-2817 to Resolved
Comment 13 Ivo Hradek 2016-11-24 13:48:43 UTC 
Verified with EAP 6.4.12.CP.CR1;
Comment 14 Petr Penicka 2017-01-17 13:12:06 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.
Note You need to log in before you can comment on or make changes to this bug.