Re: [wildfly-dev] 13 JASPIC tests failing on WildFly
Actually they seem to be registering their own AuthConfigProvider, in
which case the dummy domain setup is fine (configuring our auth-module
impl won't do anything as their provider will register their own test
module), so disregard my previous e-mail.
Note that there is a pending pull request
(https://github.com/wildfly/wildfly/pull/5558/) that seems to fix a few
of the issues seen in the tests. Lets run the tests again once the PR is
merged to and see where we stand.
Stefan
On 12/11/2013 10:52 AM, Stefan Guilhen wrote:
If you are using the security domain as mentioned in the commit any
authentication will fail because there is no "dummy" auth-module. I
couldn't find the WildFly log but there must be exceptions there
indicating it was not possible to load the auth-module class.
Try setting the auth module in the security domain to
<auth-module
code="org.wildfly.extension.undertow.security.jaspi.modules.HTTPSchemeServerAuthModule"
flag="required"/>
And see how it goes.
Stefan
On 12/10/2013 10:16 PM, Arun Gupta wrote:
> Arjan Tims has added 22 new JASPIC tests to Java EE 7 test suite at:
>
> https://github.com/javaee-samples/javaee7-samples/tree/master/jaspic
>
> 13 of them are failing with WildFly as shown at:
>
>
https://arungupta.ci.cloudbees.com/job/Java%20EE%207%20Samples%20on%20Wil...
>
> 21 of these tests are passing on GlassFish as shown at:
>
>
https://arungupta.ci.cloudbees.com/job/Java%20EE%207%20Samples%20on%20Gla...
>
> JASPIC support in WildFly is reported "broken" as mentioned at:
>
>
https://github.com/arjantijms/jaspic-capabilities-test/commit/7f78a8267b4...
>
> Adding a new <security-domain> as mentioned in the above commit
> message only marginally improves the results.
>
> Do you see any basic configuration issue with OOTB WildFly for running
> these tests ?
>
> Arun
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev