You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2018/02/18 19:20:00 UTC
[jira] [Commented] (TOMEE-2170) LogTest is broken
[ https://issues.apache.org/jira/browse/TOMEE-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16368632#comment-16368632 ]
Mark Struberg commented on TOMEE-2170:
--------------------------------------
It's actually the following 3 tests. All of them have to do with missing a scripted JAAS Realm it seems:
* arquillian/arquillian-tomee-tests/arquillian-tomee-webprofile-tests/src/test/java/org/apache/openejb/arquillian/tests/securityejb/SecurityEJBPropagationTest.java
* tomee/tomee-webaccess/src/test/groovy/org/apache/tomee/webaccess/test/units/LogTest.groovy
* tomee/tomee-webaccess/src/test/groovy/org/apache/tomee/webaccess/test/units/ScriptingTest.groovy
> LogTest is broken
> -----------------
>
> Key: TOMEE-2170
> URL: https://issues.apache.org/jira/browse/TOMEE-2170
> Project: TomEE
> Issue Type: Task
> Affects Versions: 8.0.0
> Reporter: Mark Struberg
> Priority: Major
>
> LogTest in tomee-webaccess seems to not use the configured LoginModule (JAASRealm).
>
> Wonder how this works at all as it does not contain any {{<security-constraint>. There isn't even a }}web.xml.
>
> We should finally fix this test for a final 8.0.x release. But set to @Ignore for now.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)