<div dir="ltr">Hi there,<br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 8, 2015 at 8:26 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">
<div bgcolor="#FFFFFF" text="#000000">
<div>The TCK coverage (or lack thereof) has nothing to do with the
ability to configure custom JACC providers. If we didn't support it
not a single test of the JACC testsuite would pass so the TCK is not
to be blamed in this case.</div></div></blockquote><div><br></div><div>Well, one of the requirements of JACC is that the Java EE product has a default JACC provider (which implements the authorization algorithms as defined by both the Servlet and EJB containers). So it could *theoretically* have been the case that the TCK only tests that one. Of course I don't know if this is indeed the case.</div><div><br></div><div>JBoss indeed has such a default provider. However, the spec also requires (I think) that in a full Java EE server all authorization decisions (for the APIs defined by Servlet and EJB) go via JACC, which clearly does not happen in JBoss. As far as I know, only GlassFish really does this, while TMaxSoft JEUS comes close.</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><div> The JASPIC testsuite is another story and
I think we both agree that it is broken from our previous
conversations. Arun's JEE testsuite, to which you contributed your
JASPIC tests, has been much more valuable as a tool to validate the
implementation than the TCK itself.<br></div></div></blockquote><div><br></div><div>I'm really glad they helped ;)</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><div></div>
<br>
Having said that, the documentation does really seem to be missing a
section about custom JACC providers so I went to check the TCK
setup. It looks like the TCK JACC providers are bundled in a jar and
this jar is being set as a resource of the org.jboss.as.security
module. I'm not sure why it was done this way but I believe it
should be also possible to define your own module containing the
classes and then wire it to the security module as a dependency
instead of a resource.</div></blockquote><div><br></div><div>Hmmm, how would one go about doing that exactly? I think I created a module for my custom JACC provider, then set that as a dependency for the security module (since that was the place the default implementation lives), but it again did not work (class not found exceptions). Could well be the case that I did something wrong, so an example would be great.</div><div><br></div><div>Kind regards,</div><div>Arjan Tijms</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><span class=""><br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote"><br>
<div>Those properties are of course supported, but where
does one put the classes (or jar containing these
classes)? I tried for hours at end and asked in the JBoss
forum, but it never became clear. The documentation
doesn't mention it either. See this for my question about
this: <a href="https://developer.jboss.org/thread/254106" target="_blank">https://developer.jboss.org/thread/254106</a></div>
<div><br>
</div>
<div>Would be really cool if the location could become
clear. Thanks!</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><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> <br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>Kind regards,</div>
<div>Arjan Tijms</div>
</div>
</div>
</div>
<span> <br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
wildfly-dev mailing list
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></pre>
</span></blockquote>
<br>
</div>
<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>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</span></div>
</blockquote></div><br></div></div>