[jboss-cvs] JBossAS SVN: r76684 - in branches/JBPAPP_4_3_0_GA_CC/testsuite: imports and 2 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Aug 5 14:47:04 EDT 2008
Author: pskopek at redhat.com
Date: 2008-08-05 14:47:04 -0400 (Tue, 05 Aug 2008)
New Revision: 76684
Added:
branches/JBPAPP_4_3_0_GA_CC/testsuite/imports/cc.xml
branches/JBPAPP_4_3_0_GA_CC/testsuite/src/resources/cc/
branches/JBPAPP_4_3_0_GA_CC/testsuite/src/resources/cc/cc-output-html.xsl
branches/JBPAPP_4_3_0_GA_CC/testsuite/src/resources/cc/cc-results.xsl
branches/JBPAPP_4_3_0_GA_CC/testsuite/src/resources/cc/cc-test-patterns.xsl
branches/JBPAPP_4_3_0_GA_CC/testsuite/src/resources/cc/ccTsfiMap.xsd
branches/JBPAPP_4_3_0_GA_CC/testsuite/src/resources/cc/testCaseMapping_1.0.xml
Modified:
branches/JBPAPP_4_3_0_GA_CC/testsuite/build.xml
Log:
CC evaluation testing speed up.
CC evaluation automation based on mapping file added.
Modified: branches/JBPAPP_4_3_0_GA_CC/testsuite/build.xml
===================================================================
--- branches/JBPAPP_4_3_0_GA_CC/testsuite/build.xml 2008-08-05 18:42:14 UTC (rev 76683)
+++ branches/JBPAPP_4_3_0_GA_CC/testsuite/build.xml 2008-08-05 18:47:04 UTC (rev 76684)
@@ -610,6 +610,13 @@
<exclude name="**/test/timer/test/SecureTimerUnitTestCase.class"/>
<exclude name="**/test/jmx/test/RMIAdaptorAuth*TestCase.class"/>
</patternset>
+ <!-- pattern sets for CC testing -->
+ <patternset id="cc.eap.includes" includesfile="output/eap-cc-test-patterns.txt" >
+ </patternset>
+ <patternset id="cc.ejb3.includes" includesfile="output/ejb3-cc-test-patterns.txt">
+ </patternset>
+ <patternset id="cc.jbm.includes" includesfile="output/jbm-cc-test-patterns.txt">
+ </patternset>
<!-- A patternset that requires jboss to run with a security manager -->
<patternset id="securitymgr.includes">
<include name="**/test/securitymgr/test/*TestCase.class"/>
@@ -847,13 +854,14 @@
<!-- Common Criteria Evaluation Tests running with Java Security Manager turned on.
-->
<target name="tests-cc-sm" description="Execute all Common Criteria Evaluation tests with Java Security Manager turned on."
- depends="maybejars">
+ depends="generate-cc-patternsets,maybejars">
<record name="${basedir}/build.log" append="no" action="start" loglevel="${buildlog.level}"/>
<property name="nojars" value="true"/>
<server:start name="cc-sm"/>
+ <antcall target="run-cc-tests-sm"/>
<antcall target="run-cc-tests"/>
<antcall target="tests-report"/>
@@ -865,9 +873,11 @@
</target>
+ <import file="imports/cc.xml"/>
+
<!-- Common Criteria Evaluation Tests running with Java Security Manager turned off.
-->
- <target name="tests-cc-no-sm" description="Execute all Common Criteria Evaluation tests with Java Security Manager turned off."
+ <target name="tests-cc" description="Execute all Common Criteria Evaluation tests with Java Security Manager turned off."
depends="maybejars">
<record name="${basedir}/build.log" append="no" action="start" loglevel="${buildlog.level}"/>
@@ -878,20 +888,50 @@
<antcall target="run-cc-tests"/>
<antcall target="tests-report"/>
+
+ <echo>Waiting for server to shutdown...</echo>
+ <server:stop name="cc"/>
- <echo>Waiting for server to shutdown...</echo>
- <server:stop name="cc"/>
<record name="${basedir}/build.log" action="stop"/>
</target>
<!-- Collection of all CC related tests.
- Called from both tests-cc-sm and tests-cc-no-sm targets.
+ Called from both tests-cc-sm and tests-cc targets.
Server has to be already started with proper configuration.
-->
- <target name="run-cc-tests">
+ <target name="run-cc-tests" depends="init">
+
+ <antcall target="tests-cc-unit"/>
+
+ <!--
+ <antcall target="tests-standard-unit"/>
<antcall target="tests-security-basic-unit"/>
+ -->
+
+ <!--
+ <antcall target="tomcat-ssl-tests"/>
+ -->
+ <!-- not sure about single sign on, be carefull starts own JBoss config
+ <antcall target="tomcat-sso-tests"/>
+ -->
+ <!--
+ <antcall target="tests-standard-stress"/>
+ <antcall target="tests-jbossmx-compliance"/>
+ <antcall target="tests-jbossmx-implementation"/>
+ <antcall target="tests-jbossmx-performance"/>
+ <antcall target="tests-iiop"/>
+ <antcall target="tests-scout-jaxr"/>
+ <antcall target="tests-webservice"/>
+ -->
+ </target>
+
+ <!-- Collection of CC related tests.
+ Called from tests-cc-sm target.
+ Server has to be already started with proper configuration.
+ -->
+ <target name="run-cc-tests-sm">
<antcall target="tests-security-manager-cc"/>
</target>
@@ -1718,6 +1758,86 @@
</junit>
</target>
+ <target name="tests-cc-unit">
+
+
+ <mkdir dir="${build.reports}"/>
+ <mkdir dir="${build.testlog}"/>
+ <property name="jbosstest.secure" value="true"/>
+ <property name="java.security.auth.login.config" value="${build.resources}/security/auth.conf"/>
+ <propertyset id="security-tests-props">
+ <propertyref prefix="java.security.auth"/>
+ </propertyset>
+
+ <patternset id="tests-cc-unit">
+ <patternset refid="cc.eap.includes"/>
+ <!-- Exclude securitymgr tests (the testSystemExit shuts down the cc server) -->
+ <patternset refid="securitymgr.excludes"/>
+ </patternset>
+
+ <run-junit junit.patternset="tests-cc-unit" junit.configuration="tests-security-basic-unit" junit.syspropertyset="security-tests-props"/>
+
+ </target>
+
+ <!-- TODO: This target is just for reference and should be deleted in near future -->
+ <target name="xx-tests-cc-unit">
+
+ <property name="jbosstest.secure" value="true"/>
+ <property name="java.security.auth.login.config" value="${build.resources}/security/auth.conf"/>
+ <propertyset id="security-tests-props">
+ <propertyref prefix="java.security.auth"/>
+ </propertyset>
+
+ <echo>
+ <![CDATA[
+ **** tests-cc-unit ****
+ junit.timeout: ${junit.timeout}
+ jbosstest.iterationcount: ${jbosstest.iterationcount}
+ jbosstest.threadcount: ${jbosstest.threadcount}
+ jbosstest.beancount: ${jbosstest.beancount}
+ ]]>
+ </echo>
+ <mkdir dir="${build.reports}"/>
+ <mkdir dir="${build.testlog}"/>
+ <junit dir="${module.output}" printsummary="${junit.printsummary}" haltonerror="${junit.haltonerror}" haltonfailure="${junit.haltonfailure}" fork="${junit.fork}"
+ timeout="${junit.timeout}" jvm="${junit.jvm}">
+
+ <jvmarg value="${junit.jvm.options}"/>
+ <!-- Used for JGroups -->
+ <jvmarg value="-Dbind.address=${node0}"/>
+ <sysproperty key="jboss.dist" value="${jboss.dist}"/>
+ <sysproperty key="jbosstest.deploy.dir" file="${build.lib}"/>
+ <sysproperty key="build.testlog" value="${build.testlog}"/>
+ <sysproperty key="log4j.configuration" value="file:${build.resources}/log4j.xml"/>
+ <sysproperty key="java.naming.provider.url" value="${node0.jndi.url}"/>
+ <sysproperty key="jbosstest.server.host" value="${node0}"/>
+ <sysproperty key="jboss-junit-configuration" value="tests-cc-unit"/>
+ <!-- Pass along any jbosstest.* system properties -->
+ <syspropertyset>
+ <propertyref prefix="jbosstest."/>
+ </syspropertyset>
+ <syspropertyset>
+ <propertyset refid="security-tests-props" />
+ </syspropertyset>
+
+ <classpath>
+ <pathelement location="${build.classes}"/>
+ <pathelement location="${build.resources}"/>
+ <path refid="tests.classpath"/>
+ </classpath>
+
+ <formatter type="xml" usefile="${junit.formatter.usefile}"/>
+
+ <batchtest todir="${build.reports}" haltonerror="${junit.batchtest.haltonerror}" haltonfailure="${junit.batchtest.haltonfailure}" fork="${junit.batchtest.fork}">
+
+ <fileset dir="${build.classes}">
+ <patternset refid="cc.eap.includes"/>
+ <!-- Exclude securitymgr tests (the testSystemExit shuts down the cc server) -->
+ <patternset refid="securitymgr.excludes"/>
+ </fileset>
+ </batchtest>
+ </junit>
+ </target>
<target name="tests-standard-unit" depends="init,tests-standard-unit-soa,tests-standard-unit-standard">
</target>
Added: branches/JBPAPP_4_3_0_GA_CC/testsuite/imports/cc.xml
===================================================================
--- branches/JBPAPP_4_3_0_GA_CC/testsuite/imports/cc.xml (rev 0)
+++ branches/JBPAPP_4_3_0_GA_CC/testsuite/imports/cc.xml 2008-08-05 18:47:04 UTC (rev 76684)
@@ -0,0 +1,86 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project name="Common Criteria project helper">
+
+ <target name="transform-cc-results"
+ description="Transforms results of standard test suite to the form appropriate for CC evaluation"
+ >
+
+ <!-- in="/qa/eap.bin/jboss-eap-4.3-src/jboss-as/testsuite/output/reports/TESTS-TestSuites.xml" -->
+
+ <xslt
+ in="src/resources/cc/testCaseMapping_1.0.xml"
+ out="output/cc-results.xml"
+ style="src/resources/cc/cc-results.xsl">
+
+ <outputproperty name="method" value="xml"/>
+ <outputproperty name="standalone" value="yes"/>
+ <outputproperty name="encoding" value="UTF-8"/>
+ <outputproperty name="indent" value="yes"/>
+ </xslt>
+
+
+
+ </target>
+
+ <target name="generate-cc-patternsets"
+ description="Generate patternset to use during test CC"
+ >
+
+ <xslt
+ in="src/resources/cc/testCaseMapping_1.0.xml"
+ out="output/eap-cc-test-patterns.txt"
+ style="src/resources/cc/cc-test-patterns.xsl">
+
+ <param name="testSuite" expression="EAP"/>
+
+ </xslt>
+
+ <xslt
+ in="src/resources/cc/testCaseMapping_1.0.xml"
+ out="output/ejb3-cc-test-patterns.txt"
+ style="src/resources/cc/cc-test-patterns.xsl">
+
+ <param name="testSuite" expression="EJB3"/>
+
+ </xslt>
+
+ <xslt
+ in="src/resources/cc/testCaseMapping_1.0.xml"
+ out="output/jbm-cc-test-patterns.txt"
+ style="src/resources/cc/cc-test-patterns.xsl">
+
+ <param name="testSuite" expression="JBM"/>
+
+ </xslt>
+
+ <xslt
+ in="src/resources/cc/testCaseMapping_1.0.xml"
+ out="output/cts-cc-test-patterns.txt"
+ style="src/resources/cc/cc-test-patterns.xsl">
+
+ <param name="testSuite" expression="CTS"/>
+
+ </xslt>
+
+ </target>
+
+ <target name="generate-cc-results" depends="transform-cc-results"
+ description="Generates results in user readable form">
+
+ <!--
+ <xslt
+ in="output/cc-results.xml"
+ out="output/cc-results.html"
+ style="cc-output-html.xsl">
+
+ <outputproperty name="method" value="xml"/>
+ <outputproperty name="standalone" value="yes"/>
+ <outputproperty name="encoding" value="UTF-8"/>
+ <outputproperty name="indent" value="yes"/>
+ </xslt>
+ -->
+
+
+ </target>
+
+</project>
\ No newline at end of file
Added: branches/JBPAPP_4_3_0_GA_CC/testsuite/src/resources/cc/cc-output-html.xsl
===================================================================
--- branches/JBPAPP_4_3_0_GA_CC/testsuite/src/resources/cc/cc-output-html.xsl (rev 0)
+++ branches/JBPAPP_4_3_0_GA_CC/testsuite/src/resources/cc/cc-output-html.xsl 2008-08-05 18:47:04 UTC (rev 76684)
@@ -0,0 +1,57 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsl:stylesheet version="1.0"
+ xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+ xmlns:cc="http://www.redhat.com/CcTsfiMap"
+ exclude-result-prefixes="cc">
+
+ <xsl:output method="xml" indent="yes" />
+
+ <!-- TODO: don't use absolute path -->
+ <xsl:variable name="results" select="document('/qa/eap.bin/jboss-eap-4.3-src/jboss-as/testsuite/output/reports/TESTS-TestSuites.xml')" />
+ <xsl:param name="fail.text" select="'failed'"/>
+ <xsl:param name="pass.text" select="'passed'"/>
+ <xsl:param name="not.covered.text" select="'not covered'"/>
+
+ <xsl:template match="/">
+ <xsl:for-each select="cc:testCaseMapping">
+ <xsl:for-each select="testSuite">
+ <xsl:for-each select="testCase">
+ <xsl:for-each select="test">
+
+ <xsl:variable name="package" select=""/>
+ <xsl:variable name="classname" select="../@name"/>
+ <xsl:variable name="testname" select="@name"/>
+
+ <xsl:element name="test">
+ <xsl:attribute name="testSuite">
+ <xsl:value-of select="../../@name"/>
+ </xsl:attribute>
+ <xsl:attribute name="testCase">
+ <xsl:value-of select="$classname"/>
+ </xsl:attribute>
+ <xsl:attribute name="name">
+ <xsl:value-of select="$testname"/>
+ </xsl:attribute>
+ <xsl:for-each select="TSFI">
+ <xsl:element name="tsfi"><xsl:value-of select="."/></xsl:element>
+ </xsl:for-each>
+ <xsl:element name="result">
+ <xsl:choose>
+ <xsl:when test="$results/testsuites/testsuite/testcase[@classname=$classname and @name=$testname]/failure[not(@message='')]"><xsl:value-of select="$fail.text"/></xsl:when>
+ <xsl:otherwise><xsl:value-of select="$pass.text"/></xsl:otherwise>
+ </xsl:choose>
+ </xsl:element>
+ <!--
+ <test>
+ <xsl:value-of select="../../@name"/>|<xsl:value-of select="../@name"/>|<xsl:value-of select="@name"/>
+ </test>
+ -->
+ </xsl:element>
+ </xsl:for-each>
+ </xsl:for-each>
+
+ </xsl:for-each>
+ </xsl:for-each>
+ </xsl:template>
+
+</xsl:stylesheet>
\ No newline at end of file
Added: branches/JBPAPP_4_3_0_GA_CC/testsuite/src/resources/cc/cc-results.xsl
===================================================================
--- branches/JBPAPP_4_3_0_GA_CC/testsuite/src/resources/cc/cc-results.xsl (rev 0)
+++ branches/JBPAPP_4_3_0_GA_CC/testsuite/src/resources/cc/cc-results.xsl 2008-08-05 18:47:04 UTC (rev 76684)
@@ -0,0 +1,59 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsl:stylesheet version="1.0"
+ xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+ xmlns:cc="http://www.redhat.com/CcTsfiMap"
+ exclude-result-prefixes="cc">
+
+ <xsl:output method="xml" indent="yes" />
+
+ <!-- TODO: don't use absolute path -->
+ <xsl:variable name="results" select="document('output/reports/TESTS-TestSuites.xml')" />
+ <xsl:param name="fail.text" select="'failed'"/>
+ <xsl:param name="pass.text" select="'passed'"/>
+ <xsl:param name="not.covered.text" select="'not covered'"/>
+
+ <xsl:template match="/">
+ <xsl:for-each select="cc:testCaseMapping">
+ <xsl:element name="cc-results">
+ <xsl:for-each select="testSuite">
+ <xsl:for-each select="testCase">
+ <xsl:for-each select="test">
+
+ <xsl:variable name="package" select=""/>
+ <xsl:variable name="classname" select="../@name"/>
+ <xsl:variable name="testname" select="@name"/>
+
+ <xsl:element name="test">
+ <xsl:attribute name="testSuite">
+ <xsl:value-of select="../../@name"/>
+ </xsl:attribute>
+ <xsl:attribute name="testCase">
+ <xsl:value-of select="$classname"/>
+ </xsl:attribute>
+ <xsl:attribute name="name">
+ <xsl:value-of select="$testname"/>
+ </xsl:attribute>
+ <xsl:for-each select="TSFI">
+ <xsl:element name="tsfi"><xsl:value-of select="."/></xsl:element>
+ </xsl:for-each>
+ <xsl:element name="result">
+ <xsl:choose>
+ <xsl:when test="$results/testsuites/testsuite/testcase[@classname=$classname and @name=$testname]/failure[not(@message='')]"><xsl:value-of select="$fail.text"/></xsl:when>
+ <xsl:otherwise><xsl:value-of select="$pass.text"/></xsl:otherwise>
+ </xsl:choose>
+ </xsl:element>
+ <!--
+ <test>
+ <xsl:value-of select="../../@name"/>|<xsl:value-of select="../@name"/>|<xsl:value-of select="@name"/>
+ </test>
+ -->
+ </xsl:element>
+ </xsl:for-each>
+ </xsl:for-each>
+
+ </xsl:for-each>
+ </xsl:element>
+ </xsl:for-each>
+ </xsl:template>
+
+</xsl:stylesheet>
\ No newline at end of file
Added: branches/JBPAPP_4_3_0_GA_CC/testsuite/src/resources/cc/cc-test-patterns.xsl
===================================================================
--- branches/JBPAPP_4_3_0_GA_CC/testsuite/src/resources/cc/cc-test-patterns.xsl (rev 0)
+++ branches/JBPAPP_4_3_0_GA_CC/testsuite/src/resources/cc/cc-test-patterns.xsl 2008-08-05 18:47:04 UTC (rev 76684)
@@ -0,0 +1,57 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsl:stylesheet version="2.0"
+ xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+ xmlns:cc="http://www.redhat.com/CcTsfiMap"
+ exclude-result-prefixes="cc">
+
+ <xsl:output method="text"/>
+ <xsl:param name="testSuite" select="'EAP'"/>
+
+
+ <xsl:template match="/">
+ <xsl:for-each select="cc:testCaseMapping">
+ <xsl:for-each select="testSuite">
+ <xsl:if test="@name = $testSuite">
+ <xsl:for-each select="testCase">
+ <xsl:if test="@name != ''">
+ <xsl:variable name="pattern">
+ <xsl:call-template name="replace-substring">
+ <xsl:with-param name="value" select="@name" />
+ <xsl:with-param name="from" select="'org.jboss'" />
+ <xsl:with-param name="to" select="''" />
+ </xsl:call-template>
+ </xsl:variable>
+ <xsl:text><xsl:value-of select="concat('**',translate($pattern,'.','/'),'.class')"/>
+</xsl:text>
+ </xsl:if>
+ </xsl:for-each>
+ </xsl:if>
+ </xsl:for-each>
+ </xsl:for-each>
+ </xsl:template>
+
+
+ <xsl:template name="replace-substring">
+ <xsl:param name="value" />
+ <xsl:param name="from" />
+ <xsl:param name="to" />
+ <xsl:choose>
+ <xsl:when test="contains($value,$from)">
+ <xsl:value-of select="substring-before($value,$from)" />
+ <xsl:value-of select="$to" />
+ <xsl:call-template name="replace-substring">
+ <xsl:with-param name="value"
+ select="substring-after($value,$from)" />
+ <xsl:with-param name="from" select="$from" />
+ <xsl:with-param name="to" select="$to" />
+ </xsl:call-template>
+ </xsl:when>
+ <xsl:otherwise>
+ <xsl:value-of select="$value" />
+ </xsl:otherwise>
+ </xsl:choose>
+ </xsl:template>
+
+
+</xsl:stylesheet>
+
Added: branches/JBPAPP_4_3_0_GA_CC/testsuite/src/resources/cc/ccTsfiMap.xsd
===================================================================
--- branches/JBPAPP_4_3_0_GA_CC/testsuite/src/resources/cc/ccTsfiMap.xsd (rev 0)
+++ branches/JBPAPP_4_3_0_GA_CC/testsuite/src/resources/cc/ccTsfiMap.xsd 2008-08-05 18:47:04 UTC (rev 76684)
@@ -0,0 +1,72 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
+ xmlns="http://www.redhat.com/CcTsfiMap"
+ targetNamespace="http://www.redhat.com/CcTsfiMap"
+>
+ <xsd:annotation>
+ <xsd:documentation xml:lang="en">
+ Schema for mapping document between test (test suite, test case) and TSFI.
+ This mapping is created for purpose of Common Criteria evaluation of JBoss AS.
+ </xsd:documentation>
+ </xsd:annotation>
+
+ <xsd:element name="testCaseMapping" type="TestCaseMappingType">
+ <!-- Tes suite name has to be unique, so we are enforcing it. -->
+ <xsd:unique name="testSuiteNameUnique">
+ <xsd:selector xpath="testSuite"/>
+ <xsd:field xpath="@name"/>
+ </xsd:unique>
+ </xsd:element>
+
+ <xsd:complexType name="TestCaseMappingType">
+ <xsd:sequence>
+ <xsd:element name="testSuite" type="TestSuiteType" minOccurs="1" maxOccurs="unbounded">
+
+ <xsd:unique name="testCaseNameUnique">
+ <xsd:selector xpath="testCase"/>
+ <xsd:field xpath="@name"/>
+ </xsd:unique>
+ </xsd:element>
+ </xsd:sequence>
+ </xsd:complexType>
+
+ <xsd:complexType name="TestSuiteType">
+ <xsd:sequence>
+ <xsd:element name="desc" type="xsd:string" minOccurs="0" maxOccurs="1"/>
+ <xsd:element name="testCase" type="TestCaseType" minOccurs="1" maxOccurs="unbounded">
+ <xsd:unique name="testNameUnique">
+ <xsd:selector xpath="test"/>
+ <xsd:field xpath="@name"/>
+ </xsd:unique>
+ </xsd:element>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="TestSuiteName" use="required"/>
+ </xsd:complexType>
+
+ <!-- Enumeration of all possible test suite names -->
+ <xsd:simpleType name="TestSuiteName">
+ <xsd:restriction base="xsd:string">
+ <xsd:enumeration value="EAP"/> <!-- EAP test suite -->
+ <xsd:enumeration value="CTS"/> <!-- J2EE TCK 1.4 test suite -->
+ <xsd:enumeration value="EJB3"/> <!-- EJB3 project test suite -->
+ <xsd:enumeration value="JBM"/> <!-- JBoss Messaging project test suite -->
+ <xsd:enumeration value="JBWS"/> <!-- JBoss Webservices project test suite -->
+ </xsd:restriction>
+ </xsd:simpleType>
+
+ <xsd:complexType name="TestCaseType">
+ <xsd:sequence>
+ <xsd:element name="desc" type="xsd:string" minOccurs="0" maxOccurs="1"/>
+ <xsd:element name="test" type="TestType" minOccurs="1" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ </xsd:complexType>
+
+ <xsd:complexType name="TestType">
+ <xsd:sequence>
+ <xsd:element name="desc" type="xsd:string" minOccurs="0" maxOccurs="1"/>
+ <xsd:element name="TSFI" type="xsd:string" minOccurs="1" maxOccurs="unbounded"/>
+ </xsd:sequence>
+ <xsd:attribute name="name" type="xsd:string" use="required"/>
+ </xsd:complexType>
+</xsd:schema>
Added: branches/JBPAPP_4_3_0_GA_CC/testsuite/src/resources/cc/testCaseMapping_1.0.xml
===================================================================
--- branches/JBPAPP_4_3_0_GA_CC/testsuite/src/resources/cc/testCaseMapping_1.0.xml (rev 0)
+++ branches/JBPAPP_4_3_0_GA_CC/testsuite/src/resources/cc/testCaseMapping_1.0.xml 2008-08-05 18:47:04 UTC (rev 76684)
@@ -0,0 +1,1809 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- Test Case Mapping ver. 0.1
+ TSFI ID master data:
+ - - - - - - - - - - -
+ tsfi.http - HTTP access to TOE
+ tsfi.https - HTTPS access to TOE
+
+ tsfi.rmi.jrmp - RMI over JRMP
+ tsfi.rmi.http - RMI ober HTTP
+ tsfi.rmi.https - RMI ober HTTPS
+
+ tsfi.jdbc - JDBC
+
+ tsfi.jms - JMS traffic
+
+ tsfi.ws.http - Web Services over HTTP
+ tsfi.ws.https - Web Services over HTTPS
+
+ tsfi.jmx.rmi - JMX using RMI
+
+ tsfi.start -
+ tsfi.stop -
+
+-->
+<cc:testCaseMapping xmlns:cc="http://www.redhat.com/CcTsfiMap"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://www.redhat.com/CcTsfiMap ccTsfiMap.xsd"
+>
+
+ <!-- EJB3 is a part of TOE, so we used some testcases from EJB3 project as well -->
+ <testSuite name="EJB3">
+ <testCase name="org.jboss.ejb3.test.jacc.unit.JaccTestCase">
+ <desc></desc>
+ <test name="testUnchecked">
+ <desc>?? What about tsfi.rmi.https... it also possible</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="testChecked">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="testAllEntity">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="testStarEntity">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="testSomeEntity">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="hasSecurityOrEJBException">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.ejb3.test.security.unit.EJBSpecUnitTestCase">
+ <desc>Test of EJB spec conformace using the security-spec.jar deployment unit. These test the basic role based access model.</desc>
+ <test name="testSecurityDomain">
+ <desc>Validate that the users have the expected logins and roles.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="testGetCallerPrincipal">
+ <desc>Test that:
+ 1. SecureBean returns a non-null principal when getCallerPrincipal
+ is called with a security context and that this is propagated
+ to its Entity bean ref.
+
+ 2. UnsecureBean throws an IllegalStateException when getCallerPrincipal
+ is called without a security context.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="testStatefulCreateCaller">
+ <desc>Test the use of getCallerPrincipal from within the ejbCreate in a stateful session bean</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="testDomainInteraction">
+ <desc>Test that a call interacting with different security domains does not change the</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="testPrincipalPropagation">
+ <desc>Test that the calling principal is propagated across bean calls.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="testMethodAccess">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="testDomainMethodAccess">
+ <desc>Test that the echo method is accessible by an Echo
+ role. Since the excluded() method of the StatelessSession
+ bean has been placed into the excluded set it should not
+ accessible by any user. This uses the security domain of the
+ JaasSecurityDomain service to test its use as an authentication mgr.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="testMethodAccess2">
+ <desc>Test that the permissions assigned to the stateless session bean:
+ with ejb-name=org/jboss/test/security/ejb/StatelessSession_test
+ are read correctly.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="a1testLocalMethodAccess">
+ <desc>Test a user with Echo and EchoLocal roles can access the CalleeBean
+ through its local interface by calling the CallerBean and that a user
+ with only a EchoLocal cannot call the CallerBean.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="testUncheckedRemote">
+ <desc>Test access to a bean with a mix of remote interface permissions and unchecked permissions with the unchecked permissions declared first.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="testRemoteUnchecked">
+ <desc>Test access to a bean with a mix of remote interface permissions and unchecked permissions with the unchecked permissions declared last.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="testUnchecked">
+ <desc>Test that a user with a role that has not been assigned any method permissions in the ejb-jar descriptor is able to access a method that has been marked as unchecked.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="testUncheckedWithLogin">
+ <desc>Test that a user with a valid role is able to access a bean for which all methods have been marked as unchecked.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="testExcluded">
+ <desc>Test that user scott who has the Echo role is not able to access the StatelessSession2.excluded method even though the Echo role has been granted access to all methods of StatelessSession2 to test that the excluded-list takes precendence over the method-permissions.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="testRunAs">
+ <desc>This method tests the following call chains:
+ 1. RunAsStatelessSession.echo() -> PrivateEntity.echo()
+ 2. RunAsStatelessSession.noop() -> RunAsStatelessSession.excluded()
+ 3. RunAsStatelessSession.forward() -> StatelessSession.echo()
+ 1. Should succeed because the run-as identity of RunAsStatelessSession
+ is valid for accessing PrivateEntity.
+ 2. Should succeed because the run-as identity of RunAsStatelessSession
+ is valid for accessing RunAsStatelessSession.excluded().
+ 3. Should fail because the run-as identity of RunAsStatelessSession
+ is not Echo.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="testDeepRunAs">
+ <desc> This method tests the following call chain:
+ Level1CallerBean.callEcho() -> Level2CallerBean.invokeEcho()
+ -> Level3CalleeBean.echo()
+ The Level1CallerBean uses a run-as of InternalRole and the Level2CallerBean
+ and Level3CalleeBean are only accessible by InternalRole.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="testRunAsSFSB">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="a1testMDBRunAs">
+ <desc>Test that an MDB with a run-as identity is able to access secure EJBs that require the identity.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="a1testMDBDeepRunAs">
+ <desc>Test that an MDB with a run-as identity is able to access secure EJBs
+ that require the identity. DeepRunAsMDB -> Level1MDBCallerBean.callEcho() ->
+ Level2CallerBean.invokeEcho() -> Level3CalleeBean.echo()
+ The MDB uses a run-as of InternalRole and the Level2CallerBean
+ and Level3CalleeBean are only accessible by InternalRole.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ <test name="a1testRunAsWithRoles">
+ <desc>This method tests that the RunAsWithRolesMDB is assigned multiple roles within its onMessage so that it can call into the ProjRepository session bean's methods that required ProjectAdmin, CreateFolder and DeleteFolder
+ roles.
+ </desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.rmi.http</TSFI>
+ </test>
+ </testCase>
+ <testCase name="">
+ <desc></desc>
+ <test name="">
+ <desc></desc>
+ <TSFI></TSFI>
+ </test>
+ </testCase>
+ </testSuite>
+
+ <!-- Standard EAP testsuite to TOE Security Interface mapping -->
+ <testSuite name="EAP">
+ <testCase name="org.jboss.test.security.test.CallerInfoUnitTestCase">
+ <desc>Tests of the caller context state</desc>
+ <test name="testCallerSubject">
+ <desc>Test return of a custom principal from getCallerPrincipal.</desc>
+ <TSFI>???jnp.. isn't it disabled?</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.SubjectContextUnitTestCase">
+ <desc></desc>
+ <test name="testUserMethodViaServlet">
+ <desc></desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.DeepCopySubjectUnitTestCase">
+ <desc>JBAS-2657: Add option to deep copy the authenticated subject sets
+ *
+ * Testcase that unit tests the cloneability of various JBossSX
+ * Principal/Groups
+ * Also does a test of the serverside Subject deep copy via a mutable
+ * Principal</desc>
+ <test name="testSubjectCloning">
+ <desc>Test the Deep Copy of Subjects by the JaasSecurityManager via a test servlet deployed</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.EJBSpecUnitTestCase">
+ <desc>Test of EJB spec conformace using the security-spec.jar deployment unit. These test the basic role based access model.</desc>
+ <test name="testSecurityDomain">
+ <desc>Validate that the users have the expected logins and roles.</desc>
+ <TSFI>tsfi.jmx</TSFI>
+ </test>
+ <test name="testStatefulCreateCaller">
+ <desc>Test the use of getCallerPrincipal from within the ejbCreate in a stateful session bean</desc>
+ <TSFI>???jnp.. isn't it disabled?</TSFI>
+ </test>
+ <test name="testGetCallerPrincipal">
+ <desc>Test that:
+ 1. SecureBean returns a non-null principal when getCallerPrincipal
+ is called with a security context and that this is propagated
+ to its Entity bean ref.
+
+ 2. UnsecureBean throws an IllegalStateException when getCallerPrincipal
+ is called without a security context.</desc>
+ <TSFI>???jnp.. isn't it disabled?</TSFI>
+ </test>
+ <test name="testDomainInteraction">
+ <desc>Test that a call interacting with different security domains does not change the</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testPrincipalPropagation">
+ <desc>Test that the calling principal is propagated across bean calls.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testMethodAccess">
+ <desc>Test that the echo method is accessible by an Echo
+ role. Since the noop() method of the StatelessSession
+ bean was not assigned any permissions it should be unchecked.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testDomainMethodAccess">
+ <desc>Test that the echo method is accessible by an Echo
+ role. Since the excluded() method of the StatelessSession
+ bean has been placed into the excluded set it should not
+ accessible by any user. This uses the security domain of the
+ JaasSecurityDomain service to test its use as an authentication mgr.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testMethodAccess2">
+ <desc>Test that the permissions assigned to the stateless session bean:
+ with ejb-name=org/jboss/test/security/ejb/StatelessSession_test
+ are read correctly.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testLocalMethodAccess">
+ <desc>Test a user with Echo and EchoLocal roles can access the CalleeBean
+ through its local interface by calling the CallerBean and that a user
+ with only a EchoLocal cannot call the CallerBean.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testUncheckedRemote">
+ <desc>Test access to a bean with a mix of remote interface permissions and
+ * unchecked permissions with the unchecked permissions declared first.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testRemoteUnchecked">
+ <desc>Test access to a bean with a mix of remote interface permissions and
+ * unchecked permissions with the unchecked permissions declared last.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testUnchecked">
+ <desc>Test that a user with a role that has not been assigned any
+ method permissions in the ejb-jar descriptor is able to access a
+ method that has been marked as unchecked.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testUncheckedWithLogin">
+ <desc>Test that a user with a valid role is able to access a
+ bean for which all methods have been marked as unchecked.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testExcluded">
+ <desc>Test that user scott who has the Echo role is not able to
+ access the StatelessSession2.excluded method even though
+ the Echo role has been granted access to all methods of
+ StatelessSession2 to test that the excluded-list takes
+ precendence over the method-permissions.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testRunAs">
+ <desc>This method tests the following call chains:
+ 1. RunAsStatelessSession.echo() -> PrivateEntity.echo()
+ 2. RunAsStatelessSession.noop() -> RunAsStatelessSession.excluded()
+ 3. RunAsStatelessSession.forward() -> StatelessSession.echo()
+ 1. Should succeed because the run-as identity of RunAsStatelessSession
+ is valid for accessing PrivateEntity.
+ 2. Should succeed because the run-as identity of RunAsStatelessSession
+ is valid for accessing RunAsStatelessSession.excluded().
+ 3. Should fail because the run-as identity of RunAsStatelessSession
+ is not Echo.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testDeepRunAs">
+ <desc>This method tests the following call chain:
+ Level1CallerBean.callEcho() -> Level2CallerBean.invokeEcho()
+ -> Level3CalleeBean.echo()
+ The Level1CallerBean uses a run-as of InternalRole and the Level2CallerBean
+ and Level3CalleeBean are only accessible by InternalRole.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testRunAsSFSB">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testJBAS1852">
+ <desc>Test the run-as side-effects raised in http://jira.jboss.com/jira/browse/JBAS-1852</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testMDBRunAs">
+ <desc>Test that an MDB with a run-as identity is able to access secure EJBs
+ that require the identity.</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testMDBDeepRunAs">
+ <desc>Test that an MDB with a run-as identity is able to access secure EJBs
+ that require the identity. DeepRunAsMDB -> Level1MDBCallerBean.callEcho() ->
+ Level2CallerBean.invokeEcho() -> Level3CalleeBean.echo()
+ The MDB uses a run-as of InternalRole and the Level2CallerBean
+ and Level3CalleeBean are only accessible by InternalRole.</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testRunAsWithRoles">
+ <desc>This method tests that the RunAsWithRolesMDB is assigned multiple roles
+ * within its onMessage so that it can call into the ProjRepository session
+ * bean's methods that required ProjectAdmin, CreateFolder and DeleteFolder
+ * roles.</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testHandle">
+ <desc>Test the security behavior of handles. To obtain secured bean from
+ a handle that the handle be </desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testStatefulHandle">
+ <desc>Test the security behavior of stateful handles. To obtain secured bean
+ from a handle requires that there be a security context to obtain the ejb.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testStress">
+ <desc>Stress test declarative security.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testStressNoJaasCache">
+ <desc>Stress test declarative security with the JAAS cache disabled.</desc>
+ <TSFI>tsfi.jmx.rmi</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.LoginContextUnitTestCase">
+ <desc>A JUnit TestCase for the JAAS LoginContext usage.</desc>
+ <test name="testLogin1">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testLogin2">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.NamespacePermissionsUnitTestCase">
+ <desc>A JUnit TestCase for the NamespacePermissions and NamespacePermission classes.</desc>
+ <test name="testImplied">
+ <desc>Test the NamespacePermissionCollection implies method for various permission that should be implied by the setup PermissionCollection.</desc>
+ <TSFI></TSFI>
+ </test>
+ <test name="testNotImplied">
+ <desc>Test the NamespacePermissionCollection implies method for various permission that should NOT be implied by the setup PermissionCollection.</desc>
+ <TSFI></TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.PermissionNameUnitTestCase">
+ <desc>A JUnit TestCase for the PermissionNames class.</desc>
+ <test name="testOrdering">
+ <desc>Test the order of PermissionNames</desc>
+ <TSFI></TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.WebConstraintsUnitTestCase">
+ <desc>Tests of the web declarative security model</desc>
+ <test name="testUnchecked">
+ <desc>Test URLs that should require no authentication for any method</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testGetAccess">
+ <desc>Test GETs against URLs that only allows the GET method and required the GetRole role</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testExcludedAccess">
+ <desc>Test that the excluded paths are not accessible by anyone</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testPostAccess">
+ <desc>Test POSTs against URLs that only allows the POST method and required the PostRole role</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.WebResourcePermissionUnitTestCase">
+ <desc>Tests of the JAAC WebResourcePermission</desc>
+ <test name="testCtor2">
+ <desc></desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testImpliesPermission">
+ <desc></desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testNotImpliesPermission">
+ <desc></desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testBestMatch">
+ <desc></desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testQualifiedMatch">
+ <desc></desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testQualifiedPatterns">
+ <desc></desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.WebUserDataPermissionUnitTestCase">
+ <desc>Tests of the JAAC WebUserDataPermission</desc>
+ <test name="testCtor2">
+ <desc></desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testImpliesPermission">
+ <desc></desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testNotImpliesPermission">
+ <desc></desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testMatch">
+ <desc></desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testQualifiedPatterns">
+ <desc></desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.auth.AppCallbackHandlerUnitTestCase">
+ <desc>Unit Tests the AppCallbackHandler</desc>
+ <test name="testUserNamePassword">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testMapCallback">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testByteArrayCallback">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.ejb.SFSBIntegrationTestCase">
+ <desc>Stateful Session Beans Integration Tests</desc>
+ <test name="testCallerPrincipalInSessionSynchronization">
+ <desc>Call a SFSB method that has container transaction and each of
+ * the SessionSynchronization callback methods call the getCallerPrincipal
+ *
+ * Also the SFSB has a ejb ref to another SFSB which is secured and declares
+ * a run-as role</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.jca.test.SecurityContextUnitTestCase">
+ <desc>Tests of how security context interact with the JCA layer.</desc>
+ <test name="testCallerIdentityPropagation">
+ <desc></desc>
+ <TSFI>tsfi.jdbc</TSFI>
+ </test>
+ <test name="testConfiguredIdentityPropagation">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testRunAsIdentityPropagationFS">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testRunAsIdentityPropagationDS">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.jmx.test.RMIAdaptorAuthorizationUnitTestCase">
+ <desc>Authorization of the RMI Adaptor
+ * Especially tests the usage of the authorization delegate
+ * called as org.jboss.jmx.connector.invoker.ExternalizableRolesAuthorization</desc>
+ <test name="testConfigurableRolesAuthorizedAccess">
+ <desc>Test that a valid jmx-console domain user can invoke operations
+ * through the jmx/invoker/AuthenticatedRMIAdaptor</desc>
+ <TSFI>tsfi.jmx.rmi</TSFI>
+ </test>
+ <test name="testUnAuthorizedAccess">
+ <desc>Test invalid access</desc>
+ <TSFI>tsfi.jmx.rmi</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.jmx.test.RMIAdaptorUnitTestCase">
+ <desc>Tests over the RMIAdaptor</desc>
+ <test name="testMBeanInfoMarshalling">
+ <desc>Test that we can iterate and retrieve MBeanInfo for all registered MBeans</desc>
+ <TSFI>tsfi.jmx.rmi</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.web.test.ssl.SSLUnitTestCase">
+ <desc>Tests of ssl and CLIENT-CERT auth. No basic auth.</desc>
+ <test name="testHttps">
+ <desc>Test that access of the transport constrained</desc>
+ <TSFI>tsfi.https</TSFI>
+ </test>
+ <test name="testHttpsSecurityDomain">
+ <desc></desc>
+ <TSFI>tsfi.https</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.ejb3.test.security.unit.ServletUnitTestCase">
+ <desc>Tests of servlet container integration into the JBoss server. This test
+ requires than a web container be integrated into the JBoss server. The tests
+ currently do NOT use the java.net.HttpURLConnection and associated http client
+ and these do not return valid HTTP error codes so if a failure occurs it
+ is best to connect the webserver using a browser to look for additional error
+ info.
+
+ The secure access tests require a user named 'jduke' with a password of 'theduke'
+ with a role of 'AuthorizedUser' in the servlet container.</desc>
+ <test name="testEJBServlet">
+ <desc></desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.ClientLoginModuleEJBUnitTestCase">
+ <desc>Call BeanA using jduke/theduke
+ +-- call BeanB switching idenity using ClientLoginModule
+ +---- call BeanC switching idenity using ClientLoginModule
+ validing the expected caller principal with different ejb method permissions</desc>
+ <test name="testClientLoginModule">
+ <desc></desc>
+ <TSFI>???jnp.. isn't it disabled?</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.ClientLoginModuleUnitTestCase">
+ <desc>ClientLoginModuleUnitTestCase/SecurityAssociation interaction tests</desc>
+ <test name="testSingleThreaded">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testSingleThreadedRestoreIdentity">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testSingleThreadedRestoreStack">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testMultiThreaded">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testMultiThreadedRestoreIdentity">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.CustomPrincipalPropagationUnitTestCase">
+ <desc>Test propagation of Custom Principal</desc>
+ <test name="testCustomPrincipalTransmission">
+ <desc>Custom Principal from outside the Application Server VM</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testCustomPrincipalTransmissionInVM">
+ <desc>A web-app has a welcome jsp (called as index.jsp). Inside this jsp, there is a call made out to an ejb</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.CustomSecurityManagerTestCase">
+ <desc>JBAS-2703 : Create a AuthenticationManager/AuthorizationManager
+ * plugin testcase
+ *
+ * This testcase overrides test methods from EJBSpecUnitTestCase (that
+ * should not be tested) with noop implementation.
+ *
+ * Also tests the interaction of the web layer with the EJB layer, with
+ * a custom security manager plugin installed.</desc>
+ <test name="testWebLayer">
+ <desc>Tests the access of a BASIC secured servlet that internally
+ * accesses a secured EJB</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.DynamicLoginConfigServiceUnitTestCase">
+ <desc>Unit tests for the Dynamic Login Config Service</desc>
+ <test name="testAbsoluteLoginConfigURL">
+ <desc>DynamicLoginConfig service fails absolute login-config.xml url</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testAuthConf">
+ <desc>Do not allow Null AuthConfig or login-config.xml</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.EJBPermissionUnitTestCase">
+ <desc>Tests of the JAAC EJB*Permissions</desc>
+ <test name="testCtor1">
+ <desc>Tests of the EJBMethodPermission(String name, String actions)</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testCtor2">
+ <desc>Tests of EJBMethodPermission(String ejbName, String methodInterface, Method method)</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testCtor3">
+ <desc>Tests of EJBMethodPermission(String ejbName, String methodName,
+ String methodInterface, String[] methodParams)</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.JaasSecurityDomainUnitTestCase">
+ <desc>Tests of the JaasSecurityDomain service.</desc>
+ <test name="testTmpFilePassword">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testFilePassword">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testEncodeDecode">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testEncodeDecode64">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.LoginModulesUnitTestCase">
+ <desc>Tests of the LoginModule classes.</desc>
+ <test name="testClientLogin">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testUsernamePassword">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testUsernamePasswordHash">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testUsernamePasswordHashWithDigestCallback">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testUsersRoles">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testUsersRolesHash">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testAnonUsersRoles">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testAnon">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testNull">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testIdentity">
+ <desc></desc>
+ <TSFI></TSFI>
+ </test>
+ <test name="testJCACallerIdentity">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testJaasSecurityDomainIdentityLoginModule">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testSimple">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testJdbc">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testControlFlags">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testCertLogin">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testCertRoles">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.MissingMethodUnitTestCase">
+ <desc>Tests missing-method-permissions-excluded-mode</desc>
+ <test name="testMissingIsUnchecked">
+ <desc>Test that methods without a method-permission behave as unchecked</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testMissingIsExcluded">
+ <desc>Test that methods without a method-permission behave as excluded</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.RoleMappingModuleUnitTestCase">
+ <desc>JBAS-3323: Role Mapping Login Module that maps application role to declarative role</desc>
+ <test name="testRoleMappingModule">
+ <desc>Test the RoleMappingLoginModule with no option to replace the role</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testRoleMappingModuleWithReplace">
+ <desc>Test the RoleMappingLoginModule with an option to replace the role</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.SAInheritableThreadLocalUnitTestCase">
+ <desc>Test that the security context thread locals propagate to child threads</desc>
+ <test name="testSecurityContext">
+ <desc>Test the expected security context exists via the SecurityAssociation accessors</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testInheritableThreadLocal">
+ <desc>Validate that a child thread sees its parent</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.SAThreadLocalUnitTestCase">
+ <desc>Test that the security context thread locals do NOT propagate to child threads</desc>
+ <test name="testSecurityContext">
+ <desc>Test the order of PermissionNames</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testThreadLocal">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.SecurityDomainLoginModuleOptionUnitTestCase">
+ <desc>For changes made on JBAS-1477, the security domain name is added to every login
+ * module option map by the ApplicationInfo object. When TRACE logging is enable,
+ * a login module will then display this option value for trouble shooting. The
+ * first part of test, displays how the security domain option is properly set
+ * in a security domain that exists in Configuration. The second test shows
+ * how the "other" security domain is displayed when the original domain does not
+ * exist in Configuration.</desc>
+ <test name="testSecurityDomainLoginModuleOption">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.SecurityMgrStressTestCase">
+ <desc>Stress testing of the JaasSecurityManager</desc>
+ <test name="testMTAuthentication">
+ <desc>Test concurrent access to the isValid and doesUserHaveRole security
+ * mgr methods.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.SecurityProxyUnitTestCase">
+ <desc>Tests of the EJB security proxy.</desc>
+ <test name="testMethodAccess">
+ <desc>Test that the echo method is accessible by an Echo
+ role. Since the noop() method of the StatelessSession
+ bean was not assigned any permissions it should not be
+ accessible by any user.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.SRPLoginModuleUnitTestCase">
+ <desc>Test of the secure remote password(SRP) service and its usage via JAAS
+login modules.</desc>
+ <test name="testSRPLogin">
+ <desc>Test a login against the SRP service using the SRPLoginModule</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testSRPLogins">
+ <desc>Test a login against the SRP service using the SRPLoginModule, logout,
+ * and repeat twice.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testSRPLoginHTTP">
+ <desc>Test a login against the SRP service using the SRPLoginModule</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSRPLoginHTTPHA">
+ <desc>Test a login against the SRP service using the SRPLoginModule</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSRPLoginWithExternalA">
+ <desc>Test a login against the SRP service using the SRPLoginModule and
+ specify the random number used in the client A public key.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testSRPLoginWithAuxChallenge">
+ <desc>Test a login against the SRP service using the SRPLoginModule and
+ provide an auxillarly challenge to be validated by the server.</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testSRPLoginWithMultipleSessions">
+ <desc>Test a login against the SRP service using the SRPLoginModule with
+ multiple sessions for the same user. This creates two threads</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="SRPUnitTestCase">
+ <desc>Test of the secure remote password(SRP) session key to perform crypto
+operations.</desc>
+ <test name="testEchoArgs">
+ <desc>Test that the echo method is secured by the SRPCacheLogin module</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testMultiUserEchoArgs">
+ <desc>Test that the echo method is secured by the SRPCacheLogin module when using multi-session srp with two threads</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="WebUserDataPermissionUnitTestCase">
+ <desc>Tests of the JAAC WebUserDataPermission</desc>
+ <test name="testCtor2">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testImpliesPermission">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testNotImpliesPermission">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testMatch">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testQualifiedPatterns">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.XMLLoginModulesUnitTestCase">
+ <desc>Tests of the LoginModule classes using the XMLLoginConfigImpl implementation
+ * of the JAAS login module configuration.</desc>
+ <test name="testGargantusRealm">
+ <desc></desc>
+ <TSFI></TSFI>
+ </test>
+ <test name="testPropertyReplacement">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testPBEIdentityLoginModule">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testPBEIdentityLoginModuleTmpFilePassword">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testXmlLoginModuleParsing">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testXMLLoginModule">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testXmlLoginModuleJaxbParsing">
+ <desc>JBAS-2702</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="AppCallbackHandlerUnitTestCase">
+ <desc>Unit Tests the AppCallbackHandler</desc>
+ <test name="testUserNamePassword">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testMapCallback">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testByteArrayCallback">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.securitymgr.test.EJBSpecUnitTestCase">
+ <desc>Tests of the programming restrictions defined by the EJB spec. The JBoss
+server must be running under a security manager. The securitymgr-ejb.jar
+should be granted only the following permission:
+
+grant securitymgr-ejb.jar {
+ permission java.util.PropertyPermission "*", "read";
+ permission java.lang.RuntimePermission "queuePrintJob";
+ permission java.net.SocketPermission "*", "connect";
+ };</desc>
+ <test name="testFileExists">
+ <desc>Test that a bean cannot access the filesystem using java.io.File</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testFileWrite">
+ <desc>Test that a bean cannot access the filesystem using java.io.File</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testSocketListen">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testSocketConnect">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testCreateClassLoader">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testGetContextClassLoader">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testSetContextClassLoader">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testReflection">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testThreadAccess">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testCreateThread">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testChangeSystemErr">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testCreateSecurityMgr">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testLoadLibrary">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testSystemExit">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.securitymgr.test.PolicyUnitTestCase">
+ <desc>Tests of the security permission enforcement that creates and directly
+ invokes the ejb methods to test the security policy permissions
+ without the noise of the ejb container.</desc>
+ <test name="testSecurityAssociation">
+ <desc>Test that a bean cannot access the SecurityAssociation class</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testFileIO">
+ <desc></desc>
+ <TSFI></TSFI>
+ </test>
+ <test name="testSockets">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testClassLoaders">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testReflection">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testThreadAccess">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testSystemAccess">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.securitymgr.test.SecurityUnitTestCase">
+ <desc>Tests of the security permission enforcement for items outside of the
+ standard EJB programming restrictions.</desc>
+ <test name="testGetPrincipal">
+ <desc>Test that a bean cannot access the SecurityAssociation class</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testGetCredential">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testSetPrincipal">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testSetCredential">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testGetSubject">
+ <desc>Test that access of the thread subject is allowed</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testGetSubjectCredentials">
+ <desc>Test that access to the private credentials of the thread subject fails</desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testSetSubject">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testPopRunAsRole">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="testPushRunAsRole">
+ <desc></desc>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.web.test.WebIntegrationUnitTestCase">
+ <desc>Tests of servlet container integration into the JBoss server. This test
+ requires than a web container be integrated into the JBoss server. The tests
+ currently do NOT use the java.net.HttpURLConnection and associated http client
+ and these do not return valid HTTP error codes so if a failure occurs it
+ is best to connect the webserver using a browser to look for additional error
+ info.
+
+ The secure access tests require a user named 'jduke' with a password of 'theduke'
+ with a role of 'AuthorizedUser' in the servlet container.</desc>
+ <test name="testClientLoginServlet">
+ <desc>Access the http://{host}/jbosstest/ClientLoginServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testUserInRoleServlet">
+ <desc>Access the http://{host}/jbosstest/restricted/UserInRoleServlet to
+ * test isUserInRole.</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSecureServlet">
+ <desc>Access the http://{host}/jbosstest/restricted/SecureServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSecureServlet2">
+ <desc>Access the http://{host}/jbosstest/restricted2/SecureServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSubjectServlet">
+ <desc>Access the http://{host}/jbosstest/restricted/SubjectServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSecureServletAndUnsecureAccess">
+ <desc>Access the http://{host}/jbosstest/restricted/SecureServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSecureServletWithBadPass">
+ <desc>Access the http://{host}/jbosstest/restricted/SecureServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSecureServletWithNoLogin">
+ <desc>Access the http://{host}/jbosstest/restricted/SecureServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testNotJbosstest">
+ <desc>Access the http://{host}/jbosstest-not/unrestricted/SecureServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSecuredEntityFacadeServlet">
+ <desc>Access the http://{host}/jbosstest/restricted/SecuredEntityFacadeServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSecureEJBAccess">
+ <desc>Access the http://{host}/jbosstest/restricted/SecureEJBAccess</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testIncludeEJB">
+ <desc>Access the http://{host}/jbosstest/restricted/include_ejb.jsp</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testUnsecureEJBAccess">
+ <desc>Access the http://{host}/jbosstest/UnsecureEJBAccess with method=echo
+ * to test that an unsecured servlet cannot access a secured EJB method
+ * that requires a valid permission. This should fail.</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testUnsecureAnonEJBAccess">
+ <desc>Access the http://{host}/jbosstest/UnsecureEJBAccess with method=unchecked
+ * to test that an unsecured servlet can access a secured EJB method that
+ * only requires an authenticated user. This requires unauthenticated
+ * identity support by the web security domain.</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testUnsecureRunAsServlet">
+ <desc></desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testUnsecureRunAsServletWithPrincipalName">
+ <desc>Access the http://{host}/jbosstest/UnsecureRunAsServletWithPrincipalName
+ * to test that an unsecured servlet can access a secured EJB method by using
+ * a run-as role. This should also have a custom run-as principal name.</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testUnsecureRunAsServletWithPrincipalNameAndRoles">
+ <desc>Access the http://{host}/jbosstest/UnsecureRunAsServletWithPrincipalNameAndRoles
+ * to test that an unsecured servlet can access a secured EJB method by using
+ * a run-as role. This should also have a custom run-as principal name and
+ * additional roles.</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testNotJbosstest2">
+ <desc>Deploy a second ear that include a notjbosstest-web.war to test ears
+ with the same war names conflicting.
+ Access the http://{host}/jbosstest-not2/unrestricted/SecureServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testUnauthorizedAccess">
+ <desc>JBAS-3279: Authenticated user can bypass declarative role checks for servlets</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.securitymgr.test.WebIntegrationUnitTestCase">
+ <desc>Tests of servlet container integration into the JBoss server. This test
+ requires than a web container be integrated into the JBoss server. The tests
+ currently do NOT use the java.net.HttpURLConnection and associated http client
+ and these do not return valid HTTP error codes so if a failure occurs it
+ is best to connect the webserver using a browser to look for additional error
+ info.
+
+ The secure access tests require a user named 'jduke' with a password of 'theduke'
+ with a role of 'AuthorizedUser' in the servlet container.</desc>
+ <test name="testRealPath">
+ <desc>Access the http://{host}/jbosstest/APIServlet to test the
+ * getRealPath method</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testHttpSessionListener">
+ <desc>Access the http://{host}/jbosstest/APIServlet to test the
+ * HttpSessionListener events</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testEJBOnStartupServlet">
+ <desc>Access the http://{host}/jbosstest/EJBOnStartupServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testENCServlet">
+ <desc>Access the http://{host}/jbosstest/ENCServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testServletInJar">
+ <desc>Access the http://{host}/jbosstest/SimpleServlet to test that servlets
+ * in the WEB-INF/lib jar.</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testEJBServlet">
+ <desc>Access the http://{host}/jbosstest/EJBServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testEntityServlet">
+ <desc>Access the http://{host}/jbosstest/EntityServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testStatefulSessionServlet">
+ <desc>Access the http://{host}/jbosstest/StatefulSessionServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testUserTransactionServlet">
+ <desc>Access the http://{host}/jbosstest/UserTransactionServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSpeedServlet">
+ <desc>Access the http://{host}/jbosstest/SpeedServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSnoopJSP">
+ <desc>Access the http://{host}/jbosstest/snoop.jsp</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSnoopJSPByPattern">
+ <desc>Access the http://{host}/jbosstest/snoop.jsp</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSnoopJSPByMapping">
+ <desc>Access the http://{host}/jbosstest/test-jsp-mapping</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testJSPClasspath">
+ <desc>Access the http://{host}/jbosstest/classpath.jsp</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testClientLoginServlet">
+ <desc>Access the http://{host}/jbosstest/ClientLoginServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testUserInRoleServlet">
+ <desc>Access the http://{host}/jbosstest/restricted/UserInRoleServlet to
+ * test isUserInRole.</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSecureServlet">
+ <desc>Access the http://{host}/jbosstest/restricted/SecureServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSecureServlet2">
+ <desc>Access the http://{host}/jbosstest/restricted2/SecureServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSubjectServlet">
+ <desc>Access the http://{host}/jbosstest/restricted/SubjectServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSecureServletAndUnsecureAccess">
+ <desc>Access the http://{host}/jbosstest/restricted/SecureServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSecureServletWithBadPass">
+ <desc>Access the http://{host}/jbosstest/restricted/SecureServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSecureServletWithNoLogin">
+ <desc>Access the http://{host}/jbosstest/restricted/SecureServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testNotJbosstest">
+ <desc>Access the http://{host}/jbosstest-not/unrestricted/SecureServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSecuredEntityFacadeServlet">
+ <desc>Access the http://{host}/jbosstest/restricted/SecuredEntityFacadeServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSecureEJBAccess">
+ <desc>Access the http://{host}/jbosstest/restricted/SecureEJBAccess</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testIncludeEJB">
+ <desc>Access the http://{host}/jbosstest/restricted/include_ejb.jsp</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testUnsecureEJBAccess">
+ <desc>Access the http://{host}/jbosstest/UnsecureEJBAccess with method=echo
+ * to test that an unsecured servlet cannot access a secured EJB method
+ * that requires a valid permission. This should fail.</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testUnsecureAnonEJBAccess">
+ <desc>Access the http://{host}/jbosstest/UnsecureEJBAccess with method=unchecked
+ * to test that an unsecured servlet can access a secured EJB method that
+ * only requires an authenticated user. This requires unauthenticated
+ * identity support by the web security domain.</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testUnsecureRunAsServlet">
+ <desc></desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testUnsecureRunAsServletWithPrincipalName">
+ <desc>Access the http://{host}/jbosstest/UnsecureRunAsServletWithPrincipalName
+ * to test that an unsecured servlet can access a secured EJB method by using
+ * a run-as role. This should also have a custom run-as principal name.</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testUnsecureRunAsServletWithPrincipalNameAndRoles">
+ <desc>Access the http://{host}/jbosstest/UnsecureRunAsServletWithPrincipalNameAndRoles
+ * to test that an unsecured servlet can access a secured EJB method by using
+ * a run-as role. This should also have a custom run-as principal name and
+ * additional roles.</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testNotJbosstest2">
+ <desc>Deploy a second ear that include a notjbosstest-web.war to test ears
+ with the same war names conflicting.
+ Access the http://{host}/jbosstest-not2/unrestricted/SecureServlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testBadWarRedeploy">
+ <desc>Deploy a bad war and then redploy with a fixed war to test failed war
+ * cleanup.
+ * Access the http://{host}/redeploy/index.html</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testWarManifest">
+ <desc>Test of a war that accesses classes referred to via the war manifest
+ * classpath. Access the http://{host}/manifest/classpath.jsp</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testBadEarRedeploy">
+ <desc></desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testJava2ClassLoadingComplianceOverride">
+ <desc>Validate a war level override of the
+ * java2ClassLoadingComplianceOverride flag to true with a
+ * useJBossWebLoader = false</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testJava2ClassLoadingComplianceOverrideULR">
+ <desc>Validate a war level override of the
+ * java2ClassLoadingComplianceOverride flag to true with a
+ * useJBossWebLoader = true</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testUnauthorizedAccess">
+ <desc>JBAS-3279: Authenticated user can bypass declarative role checks for servlets</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.web.security.CustomHeaderAuthTestCase">
+ <desc>JBAS-2283: Custom Header based authentication</desc>
+ <test name="testRegularFormAuth">
+ <desc>Ensure that in the absence of headers, there is regular
+ * form based authentication</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.web.test.ClusteredSingleSignOnUnitTestCase">
+ <desc>Tests of web app single sign-on in a clustered environment</desc>
+ <test name="testUndeployNonClusteredWebapp">
+ <desc></desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testUndeployClusteredWebapp">
+ <desc></desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testFormAuthSingleSignOn">
+ <desc>Test single sign-on across two web apps using form based auth</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testNoAuthSingleSignOn">
+ <desc>Test single sign-on across two web apps using form based auth</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSessionExpiration">
+ <desc>Tests that use of transactions in ClusteredSSO does not interfere
+ * with session expiration thread. See JBAS-2212.</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ </testCase>
+ <testCase name="FormAuthUnitTestCase">
+ <desc>Tests of form authentication</desc>
+ <test name="testFormAuth">
+ <desc>Test form authentication of a secured servlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testFormAuthException">
+ <desc>Test that a bad login is redirected to the errors.jsp and that the
+ * session j_exception is not null.
+ * </desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testFormAuthSubject">
+ <desc>Test form authentication of a secured servlet and validate that there is
+ * a SecurityAssociation setting Subject. </desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testPostDataFormAuth">
+ <desc>Test that a post from an unsecured form to a secured servlet does not
+ * loose its data during the redirct to the form login.</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testFlushOnSessionInvalidation">
+ <desc>Test that the war which use <security-domain flushOnSessionInvalidation="true">
+ * in the jboss-web.xml does not have any jaas security domain cache entries
+ * after the web session has been invalidated.</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.web.test.SingleSignOnUnitTestCase">
+ <desc>ests of web app single sign-on</desc>
+ <test name="testFormAuthSingleSignOn">
+ <desc>Test single sign-on across two web apps using form based auth</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testNoAuthSingleSignOn">
+ <desc>Test single sign-on across two web apps using form based auth</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.web.test.UserInRoleUnitTestCase">
+ <desc>Tests of the servlet request isUserInRole call.</desc>
+ <test name="testRoleWithLink">
+ <desc>Test that the custom 404 error page is seen</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testRoleWithoutLink">
+ <desc></desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testConflictingUserInRole">
+ <desc>Test that two wars from different security domains with common principal
+ * names do not conflict in terms of isUserInRole results.
+ * http://jira.jboss.com/jira/browse/JBAS-3043
+ *
+ * This is the non-jacc version where the programmatic security of isUserInRole
+ * will work off of the roles populated in the subject, irrespective of whether
+ * the roles are fully defined in the web.xml</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testConflictingUserInRoleJaccVersion">
+ <desc>Test that two wars from different security domains with common principal
+ * names do not conflict in terms of isUserInRole results.
+ * http://jira.jboss.com/jira/browse/JBAS-3043
+ *
+ * This is the jacc version where the programmatic security of isUserInRole
+ * will work only of the roles are fully defined in the web.xml</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.web.test.WebProgrammaticLoginTestCase">
+ <desc>JBAS-4077: Web Programmatic Login </desc>
+ <test name="testUnsuccessfulLogin">
+ <desc>Test unsuccessful login</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSuccessfulLogin">
+ <desc>Test Successful programmatic login in a servlet</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.jmx.test.SecureRMIAdaptorUnitTestCase">
+ <desc>Tests for a secured deployment of the jmx invoker adaptor</desc>
+ <test name="testAuthenticatedAccess">
+ <desc>Test that a valid jmx-console domain user can invoke operations
+ * through the jmx/invoker/AuthenticatedRMIAdaptor</desc>
+ <TSFI>tsfi.jmx.rmi</TSFI>
+ </test>
+ <test name="testUnauthenticatedAccess">
+ <desc>Test that a valid jmx-console domain user can NOT invoke operations
+ * through the jmx/invoker/AuthenticatedRMIAdaptor</desc>
+ <TSFI>tsfi.jmx.rmi</TSFI>
+ </test>
+ <test name="testAuthorizedAccess">
+ <desc>Test that a valid jmx-console domain user can invoke operations
+ * through the jmx/invoker/AuthenticatedRMIAdaptor</desc>
+ <TSFI>tsfi.jmx.rmi</TSFI>
+ </test>
+ <test name="testUnauthorizedAccess">
+ <desc>Test that a valid jmx-console domain user can NOT invoke operations
+ * through the jmx/invoker/AuthenticatedRMIAdaptor</desc>
+ <TSFI>tsfi.jmx.rmi</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.naming.test.SecurityUnitTestCase">
+ <desc>Tests of secured access to the JNDI naming service. This testsuite will be run with the standard security resources available via the classpath.</desc>
+ <test name="testSecureHttpInvokerFailure">
+ <desc>Test access to the security http InitialContext without a login</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testSecureHttpInvoker">
+ <desc>Test access to the JNDI naming service over a restricted http URL</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testHttpReadonlyLookup">
+ <desc>Test access of the readonly context without a login</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testHttpReadonlyContextLookup">
+ <desc>Test access of the readonly context without a login</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="testLoginInitialContext">
+ <desc>Test an initial context factory that does a JAAS login to validate the credentials passed in</desc>
+ <TSFI>???jnp.. isn't it disabled?</TSFI>
+ </test>
+ <test name="testSecureEJBViaLoginInitialContextFactory">
+ <desc>Use the LoginInitialContextFactory to access a secured ejb</desc>
+ <TSFI>???jnp.. isn't it disabled?</TSFI>
+ </test>
+ <test name="testSecureEJBViaJndiLoginInitialContextFactory">
+ <desc>Use the JndiLoginInitialContextFactory to access a secured ejb</desc>
+ <TSFI>???jnp.. isn't it disabled?</TSFI>
+ </test>
+ <test name="testEjbLinkLocalSecured">
+ <desc></desc>
+ <TSFI>???jnp.. isn't it disabled?</TSFI>
+ </test>
+ </testCase>
+
+ <!-- template -->
+ <testCase name="">
+ <desc></desc>
+ <test name="">
+ <desc></desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ </testCase>
+
+ </testSuite>
+
+ <testSuite name="JBM">
+
+ <testCase name="org.jboss.test.messaging.jms.SecurityTest">
+ <desc>Test JMS Security. This test must be run with the Test security config. on the server.</desc>
+ <test name="testLoginNoUserNoPassword ">
+ <desc>Login with no user, no password. Should allow login (equivalent to guest)</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testLoginValidUserAndPassword">
+ <desc>Login with valid user and password
+ * Should allow</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testLoginValidUserInvalidPassword">
+ <desc>Login with valid user and invalid password</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testLoginInvalidUserInvalidPassword">
+ <desc>Login with invalid user and invalid password</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testPreConfClientID">
+ <desc>user/pwd with preconfigured clientID, should return preconf</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testSetClientID">
+ <desc>Try setting client ID</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testSetClientIDPreConf">
+ <desc>Try setting client ID on preconfigured connection - should throw exception</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testAnonymousConnection">
+ <desc>Authorization tests</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testValidTopicPublisher">
+ <desc></desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testInvalidTopicPublisher">
+ <desc></desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testValidTopicSubscriber">
+ <desc></desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testInvalidTopicSubscriber">
+ <desc></desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testValidQueueBrowser">
+ <desc></desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testInvalidQueueBrowser">
+ <desc></desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testValidQueueSender">
+ <desc></desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testInvalidQueueSender">
+ <desc></desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testValidQueueReceiver">
+ <desc></desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testInvalidQueueReceiver">
+ <desc></desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testValidDurableSubscriptionCreationPreConf">
+ <desc>Test valid durable subscription creation for connection preconfigured with client id</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testInvalidDurableSubscriptionCreationPreConf">
+ <desc> Test invalid durable subscription creation for connection preconfigured with client id</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testValidDurableSubscriptionCreationNotPreConf">
+ <desc>Test valid durable subscription creation for connection not preconfigured with client id</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testInvalidDurableSubscriptionCreationNotPreConf">
+ <desc>Test invalid durable subscription creation for connection not preconfigured with client id</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testDefaultSecurityValid">
+ <desc></desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testDefaultSecurityInvalid">
+ <desc></desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testDefaultSecurityUpdate">
+ <desc>This test makes sure that changing the default security configuration on the server has effect over already deployed destinations.</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testQueueSecurityUpdateStopped">
+ <desc>This test makes sure that changing the queue security configuration on the server has effect
+ * over destinations when they are stopped (this is what happens in a real deployment - the security config
+ * gets set before the queue/topic is started
+ * See http://jira.jboss.com/jira/browse/JBMESSAGING-976</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testTopicSecurityUpdateStopped">
+ <desc> * This test makes sure that changing the topic security configuration on the server has effect
+ * over destinations when they are stopped (this is what happens in a real deployment - the security config
+ * gets set before the queue/topic is started
+ * See http://jira.jboss.com/jira/browse/JBMESSAGING-976</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testQueueSecurityUpdate">
+ <desc>This test makes sure that changing the queue security configuration on the server has effect
+ * over already deployed destinations.</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testTopicSecurityUpdate">
+ <desc>This test makes sure that changing the topic security configuration on the server has effect
+ * over already deployed destinations.</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testSecurityForQueuesAndTopicsWithTheSameName">
+ <desc></desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testSecurityForTemporaryQueue">
+ <desc></desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testSecurityForTemporaryTopic">
+ <desc></desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testSecurityForTemporaryDestination">
+ <desc></desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testSecurityOnXA">
+ <desc>This Validate sending messages on an Queue where the user don't have write authorization</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.thirdparty.jbosssx.SecurityAssociationTest">
+ <desc>Set of tests to insure consistent behavior relative to the JBoss AS security infrastructure.
+ * This is just a safety layer, full fledged security tests should be present in the integration
+ * test suite.</desc>
+ <test name="testSecurityAssociation">
+ <desc></desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testGuestAuthorizedSend">
+ <desc>Send a message to a queue that requires write permissions, and make sure the thread local
+ * SecurityContext stack is correctly cleaned up after that. We're using a test security
+ * manager that simulates a JBoss JaasSecurityManager.</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ <test name="testAuthorizedSend">
+ <desc>Send a message to a queue that requires write permissions, and make sure the thread local
+ * SecurityContext stack is correctly cleaned up after that. We're using a test security
+ * manager that simulates a JBoss JaasSecurityManager.</desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ </testCase>
+ <testCase name="org.jboss.test.security.test.HttpsUnitTestCase">
+ <desc>Test of using https urls inside of the JBoss server. This testcase
+ creates a simple https server and deploys a service that tries to
+ connect to the server using the https url passed to the service.</desc>
+ <test name="testJSSE">
+ <desc>Test the JSSE installation</desc>
+ <TSFI>tsfi.https</TSFI>
+ </test>
+ <test name="testHttpsURL">
+ <desc>Test a login against the SRP service using the SRPLoginModule</desc>
+ <TSFI>tsfi.https</TSFI>
+ </test>
+ </testCase>
+
+ <!-- template -->
+ <testCase name="">
+ <desc></desc>
+ <test name="">
+ <desc></desc>
+ <TSFI>tsfi.jms</TSFI>
+ </test>
+ </testCase>
+
+ </testSuite>
+
+ <!-- JBoss (TOE) has passed J2EE TCK 1.4, so some testcases from there are also picked up -->
+ <testSuite name="CTS">
+ <testCase name="J2EE">
+ <desc>J2EETM 1.4 Platform assertions</desc>
+ <test name="J2EE:SPEC:21">
+ <desc> All J2EE products are required to support three login mechanisms: HTTP basic authentication, SSL mutual authentication, and form-based login. An application is not required to use any of these mechanisms, but they are required to be available for any application's use.</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="J2EE:SPEC:22">
+ <desc>All J2EE products are required to support HTTP basic authentication (RFC2068). Platform Providers are also required to support basic authentication over SSL.</desc>
+ <TSFI>tsfi.http</TSFI>
+ <TSFI>tsfi.https</TSFI>
+ </test>
+ <test name="J2EE:SPEC:25">
+ <desc>Web containers are required to support access to web resources by clients that have not authenticated themselves to the container. This is the common mode of access to web resources on the Internet. A web container reports that no user has been authenticated by returning null from the HttpServletRequest method getUserPrincipal. This is different than the corresponding result for EJB containers. The EJB specification requires that the EJBContext method getCallerPrincipal always return a valid Principal object. The method can never return null. Components running in a web container must be able to call enterprise beans even when no user has been authenticated in the web container. When a call is made in such a case from a component in a web container to an enterprise bean, a J2EE product must provide a principal for use in the call. A J2EE product may provide a principal for use by unauthenticated callers using many approaches, including, but not limited to: Alw!
ays use a single distinguished principal. Use a different distinguished principal per server, or per session, or per application. Allow the deployer or system administrator to choose which principal to use through the Run As capability of the web and enterprise bean containers. </desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="J2EE:SPEC:27">
+ <desc>A Product Provider must support both of the following: 1. Configured Identity.AJ2EE container must be able to authenticate for access to the resource using a principal and authentication data specified by a Deployer at deployment time.The authentication must not depend in any way on data provided by the application components. Providing for the confidential storage of the authentication information is the responsibility of the Product Provider. 2. Programmatic Authentication. The J2EE product must provide for specification of the principal and authentication data for a resource by the application component at runtime using appropriate APIs. The application may obtain the principal and authentication data through a variety of mechanisms, including receiving them as parameters, obtaining them from the component's environment, and so forth.</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="J2EE:SPEC:30">
+ <desc> Caller Authorization A J2EE product must enforce the access control rules specified at deployment time (see Section J2EE.3.6, Deployment Requirements) and more fully described in the EJB and servlet specifications.</desc>
+ <TSFI>tsfi.http</TSFI>
+ <TSFI>tsfi.rmi.jrmp</TSFI>
+ </test>
+ <test name="J2EE:SPEC:31">
+ <desc> Propagated Caller Identities. It must be possible to configure a J2EE product so that a propagated caller identity is used in all authorization decisions. With this configuration, for all calls to all enterprise beans from a single application within a single J2EE product, the principal name returned by the EJBContext method getCallerPrincipal must be the same as that returned by the first enterprise bean in the call chain. If the first enterprise bean in the call chain is called by a servlet or JSP page, the principal name must be the same as that returned by the HttpServletRequest method getUserPrincipal in the calling servlet or JSP page. (However, if the HttpServletRequest method getUserPrincipal returns null, the principal used in calls to enterprise beans is not specified by this specification, although it must still be possible to configure enterprise beans to be callable by such components.) Note that this does not require delegation of credentials, o!
nly identification of the caller. A single principal must be the principal used in authorization decisions for access to all enterprise beans in the call chain. The requirements in this section apply only when a J2EE product has been configured to propagate caller identity</desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="J2EE:SPEC:33">
+ <desc> All J2EE products must implement the access control semantics described in the EJB, JSP, and servlet specifications, and provide a means of mapping the deployment descriptor security roles to the actual roles exposed by a J2EE product </desc>
+ <TSFI>tsfi.http</TSFI>
+ </test>
+ <test name="">
+ <desc></desc>
+ <TSFI></TSFI>
+ </test>
+ </testCase>
+
+ <!-- template -->
+ <testCase name="">
+ <desc></desc>
+ <test name="">
+ <desc></desc>
+ <TSFI></TSFI>
+ </test>
+ </testCase>
+ </testSuite>
+
+</cc:testCaseMapping>
\ No newline at end of file
More information about the jboss-cvs-commits
mailing list