<div dir="ltr">Hi,<div><br></div><div>I fixed the tests so they don't throw exceptions anymore after a 403. Using a SNAPSHOT build from January 11, things start to get better now :)</div><div><br></div><div><div>[INFO] common ............................................ SUCCESS [1.422s]</div>
<div>[INFO] basic-authentication .............................. SUCCESS [5.315s]</div><div>[INFO] ejb-propagation ................................... FAILURE [5.010s]</div><div>[INFO] lifecycle ......................................... FAILURE [3.747s]</div>
<div>[INFO] register-session .................................. FAILURE [4.160s]</div><div>[INFO] wrapping .......................................... SUCCESS [3.739s]</div></div><div><br></div><div>ejb-propagation even partially succeeds. The authentication details are available in the public EJB bean (EJB bean without a security interceptor for @RolesAllowed), but access to a protected EJB (EJB bean with the security interceptor) fails.</div>
<div><br></div><div>This looks exactly like the bug in JBoss EAP 6.x. The security interceptor always tries to authenticate with the "security domain", where it expects a proprietary JBoss login module. I think the interceptor should just use the identity of the caller for local calls (calls to local EJB beans).</div>
<div><br></div><div>If I'm not mistaken, the entire reason to consult a security domain for every method call to an EJB bean is for remote EJB beans, not for local ones. I agree, the spec is not clear about this, but I think other servers indeed use the authenticated identity of the caller for local calls. See also the issue logged for EAP 6.x: <a href="https://issues.jboss.org/browse/SECURITY-746">https://issues.jboss.org/browse/SECURITY-746</a></div>
<div><br></div><div>lifecycle is also failing, but this should hopefully be rather simple to fix.<br></div><div><br></div><div>register-session may be a bit more tricky. I remember it took the GlassFish guys some effort.</div>
<div><br></div><div>Btw, there are some things that historically failed on JBoss for which I haven't created tests yet, like forwarding and including from a SAM, which are now mandatory for JASPIC 1.1 (but which the TCK probably doesn't test for either).</div>
<div><br></div><div>Kind regards,</div><div>Arjan Tijms</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div>
<div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 9, 2014 at 10:28 PM, arjan tijms <span dir="ltr"><<a href="mailto:arjan.tijms@gmail.com" target="_blank">arjan.tijms@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im HOEnZb"><div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">That's very good news Stefan!</span><div style="font-family:arial,sans-serif;font-size:13px">
<br></div><div style="font-family:arial,sans-serif;font-size:13px">
I'll also take a look at the 403/Exception that you mentioned before. Indeed, HttpUnit throws an exception upon a 403 where Drone that I used for the original tests didn't. This will probably also fix a few test breakages.</div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">Kind regards,</div><div style="font-family:arial,sans-serif;font-size:13px">Arjan</div></div></div>
<div class="HOEnZb"><div class="h5"><div class="gmail_extra">
<br><br><div class="gmail_quote">On Thu, Jan 9, 2014 at 9:06 PM, Stefan Guilhen <span dir="ltr"><<a href="mailto:sguilhen@redhat.com" target="_blank">sguilhen@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I've put a PR for a commit that fixes the wrapping tests. Remaining<br>
failures have been analysed and will be fixed soon.<br>
<div><div><br>
On 01/09/2014 03:32 PM, Arun Gupta wrote:<br>
> Arjan,<br>
><br>
> 5 test failures have gone down for now, jboss-web.xml is added to them for now.<br>
><br>
> Arun<br>
><br>
> On Thu, Jan 9, 2014 at 3:51 AM, Tomaž Cerar <<a href="mailto:tomaz.cerar@gmail.com" target="_blank">tomaz.cerar@gmail.com</a>> wrote:<br>
>> You can find info about nightly builds here<br>
>> <a href="https://community.jboss.org/thread/224262" target="_blank">https://community.jboss.org/thread/224262</a><br>
>><br>
>> but just wait a bit for new build that is currently building, that one will<br>
>> have changes you want.<br>
>><br>
>> --<br>
>> tomaz<br>
>><br>
>><br>
>> On Thu, Jan 9, 2014 at 12:11 PM, arjan tijms <<a href="mailto:arjan.tijms@gmail.com" target="_blank">arjan.tijms@gmail.com</a>> wrote:<br>
>>> Hi,<br>
>>><br>
>>><br>
>>> On Thu, Jan 9, 2014 at 12:07 PM, Tomaž Cerar <<a href="mailto:tomaz.cerar@gmail.com" target="_blank">tomaz.cerar@gmail.com</a>><br>
>>> wrote:<br>
>>>> Hey,<br>
>>>><br>
>>>> this PR <a href="https://github.com/wildfly/wildfly/pull/5683" target="_blank">https://github.com/wildfly/wildfly/pull/5683</a> was merged<br>
>>>> yesterday, can you check if it fixes any of your problems?<br>
>>><br>
>>> I'll check it out, thanks! Any convenient place where I can download a<br>
>>> nightly WildFly build?<br>
>>><br>
>>><br>
>>><br>
>>><br>
>>>><br>
>>>> --<br>
>>>> tomaz<br>
>>>><br>
>>>><br>
>>>> On Wed, Jan 8, 2014 at 11:32 PM, arjan tijms <<a href="mailto:arjan.tijms@gmail.com" target="_blank">arjan.tijms@gmail.com</a>><br>
>>>> wrote:<br>
>>>>> Hi,<br>
>>>>><br>
>>>>>> On Thu, Dec 12, 2013 at 6:57 PM, Stefan Guilhen <<a href="mailto:sguilhen@redhat.com" target="_blank">sguilhen@redhat.com</a>><br>
>>>>>> wrote:<br>
>>>>>>> These are all valid points and I agree that our implementation could<br>
>>>>>>> use some improvements. I'll create a document with the points that need to<br>
>>>>>>> be addressed and I propose we discuss them further next week when Pedro<br>
>>>>>>> returns from his vacations.<br>
>>>>><br>
>>>>><br>
>>>>> Just wondering if there has been some progress in the meantime. The<br>
>>>>> JASPIC tests unfortunately still don't run at all on WildFly.<br>
>>>>><br>
>>>>> I do have to update the tests to HtmlUnit though, and check whether<br>
>>>>> there is or isn't an exception after a 403. The original tests were based on<br>
>>>>> Drone and that one didn't threw an exception. GlassFish doesn't return a 403<br>
>>>>> by itself but just a blank response, so that's why I didn't catch this one<br>
>>>>> earlier.<br>
>>>>><br>
>>>>> Anyway, it would be great if we can work together to get the tests to<br>
>>>>> run.<br>
>>>>><br>
>>>>> Kind regards,<br>
>>>>> Arjan<br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> _______________________________________________<br>
>>>>> wildfly-dev mailing list<br>
>>>>> <a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
>>>>> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
>>>><br>
>><br>
>> _______________________________________________<br>
>> wildfly-dev mailing list<br>
>> <a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
><br>
><br>
<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>