Bug 724267 (BRMS-212) - wrong authentication method set
Summary: wrong authentication method set
Keywords:
Status: CLOSED NEXTRELEASE
Alias: BRMS-212
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: BRM (Guvnor)
Version: 5.0.1 CR1
Hardware: Unspecified
OS: Unspecified
urgent
unspecified
Target Milestone: ---
: 5.0.1,5.0.1 CR2
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-25 10:00 UTC by Jaroslaw Kijanowski
Modified: 2010-09-03 09:57 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
5.0.1. CR1
Last Closed: 2009-09-18 08:01:14 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 724149 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Issue Tracker BRMS-212 0 None None None Never

Internal Links: 724149

Description Jaroslaw Kijanowski 2009-08-25 10:00:09 UTC 
Date of First Response: 2009-08-25 10:50:39
securitylevel_name: Public

The "defaultAuthenticator.authenticate" method has been set instead of "authenticator.authenticate" which uses a jaas config.
Comment 1 trev 2009-08-25 14:48:09 UTC 
Link: Added: This issue is related to BRMS-92
Comment 2 trev 2009-08-25 14:50:39 UTC 
will be fixed in CR2
Comment 3 trev 2009-08-26 16:11:11 UTC 
fixed in drool-guvnor/soa-specific.xml 
revision 29081
Comment 4 David Le Sage 2009-09-10 06:16:07 UTC 
Please confirm the following for the Release Notes documentation:

The CAUSE (what was actually broken)
 * the wrong authentication method was set

CONSEQUENCES of the bug (how it impacts users.)
 * unless an external authentication system was utilised, users and administrators were not required to submit passwords to access the system.

The FIX (what was changed to eliminate this bug) and 
 * The security method has now been changed to be the same as that for the jmx-console. This has also been documented.

RESULTS of the fix (what now happens for users.)
 *  Users are now required to submit passwords in order to access the system.
Comment 5 Jaroslaw Kijanowski 2009-09-10 08:11:44 UTC 
This is a bug that affects the internal CR1 release - I've already changed the Affects version. No need to put it into rel notes.
Comment 6 David Le Sage 2009-09-15 04:04:21 UTC 
Thanks for that quick feedback, Jaroslaw.  We will leave it out.  


Cheers,

David
Comment 7 Jaroslaw Kijanowski 2009-09-18 08:01:14 UTC 
Verified in 5.0.1 CR2
Note You need to log in before you can comment on or make changes to this bug.