View results here -> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.0?log=log20040922185057Lbuild.31

BUILD COMPLETE -  build.31
Date of build: 09/22/2004 18:50:57
Time to build: 24 minutes 23 seconds
Last changed: 09/22/2004 18:03:59
Last log entry: Update the isUserInRole tests

 Unit Tests: (0)
 

 Modifications since last build:  (8)
1.22.2.1modifiedstarksmtestsuite/src/main/org/jboss/test/web/test/WebIntegrationUnitTestCase.javaUpdate the isUserInRole tests
1.2.6.1deletedstarksmtestsuite/src/resources/web/scripts/SecurityConfig.bshUpdate the isUserInRole tests
1.7.2.1modifiedstarksmtestsuite/src/resources/web/html/jbosstest/index.htmlUpdate the isUserInRole tests
1.13.2.1modifiedstarksmtestsuite/src/resources/web/WEB-INF/jbosstest-web.xmlUpdate the isUserInRole tests
1.2.6.1modifiedstarksmtestsuite/src/resources/web/META-INF/jboss-app.xmlUpdate the isUserInRole tests
1.2.6.1modifiedstarksmtestsuite/src/main/org/jboss/test/jmx/test/JMXConsoleUnitTestCase.javaUpdate the HttpUtils usage
1.2.6.1modifiedstarksmtestsuite/src/main/org/jboss/test/util/web/HttpUtils.javaReturn the HttpMethodBase rather than the HttpClient so that additional information like headers may be obtained from the request.
1.1.2.1modifiedstarksmtomcat/src/main/org/jboss/web/tomcat/security/CustomPrincipalValve.javaOverriding the request user principal was causing the request isUserInRole call to fail when the base realm tried to validate the cached principal. This valve now replaces the incoming request with a wrapper which overrides the request getUserPrincipal to return the true principal established by the realm during authentication.

Reply via email to