[
http://jira.jboss.com/jira/browse/JBAS-5275?page=comments#action_12401310 ]
Martin Malina commented on JBAS-5275:
-------------------------------------
Solution:
The following line needs to be changed:
============================
assertTrue("roles in (Role2, Role3)",
roleNames[0].equals("Role2") &&
roleNames[1].equals("Role3"));
===========================================
to
===============================
//Take care of Map implementations on various platforms
assertTrue("roles in (Role2, Role3)",
roleNames[0].equals("Role2") &&
roleNames[1].equals("Role3") ||
roleNames[0].equals("Role3") &&
roleNames[1].equals("Role2"));
org.jboss.test.security.test.XMLLoginModulesUnitTestCase failing on
Z-servers
-----------------------------------------------------------------------------
Key: JBAS-5275
URL:
http://jira.jboss.com/jira/browse/JBAS-5275
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite
Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
Environment: Java Version 1.5.0
Java Vendor IBM Corporation
Java VM Name IBM J9 VM
Java VM Version 2.3
Java VM Info J2RE 1.5.0 IBM J9 2.3 Linux s390-31 j9vmxz3123-20070426 (JIT enabled) J9VM -
20070420_12448_bHdSMr JIT - 20070419_1806_r8 GC - 200704_19
OS Name Linux
OS Version 2.6.9-55.EL
OS Arch s390
Reporter: Martin Malina
Assigned To: Martin Malina
Fix For: JBossAS-4.2.3.GA, JBossAS-5.0.0.CR1
Getting this:
testXmlLoginModuleParsing Failure roles in (Role2, Role3)
junit.framework.AssertionFailedError: roles in (Role2, Role3)
at
org.jboss.test.security.test.XMLLoginModulesUnitTestCase.testXmlLoginModuleParsing(XMLLoginModulesUnitTestCase.java:210)
I found out that for some reason when the testsuite is run on Z-systems with IBM 1.5
JDK, the roles from the XML file load in backwards order. That's the only problem
here. This is the piece of the XML:
<lm:user name="jdukeman"
password="anotherduke">
<lm:role name="Role2"/>
<lm:role name="Role3"/>
<lm:role name="callerJdukeman"
group="CallerPrincipal" />
</lm:user>
So the problem is that Role3 is loaded as first and Role2 as second which is causing the
failure.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira