<div dir="ltr">Hi,<br><div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 5, 2014 at 10:50 AM, Darran Lofthouse <span dir="ltr"><<a href="mailto:darran.lofthouse@jboss.com" target="_blank">darran.lofthouse@jboss.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">+1 Recently looking at how different JDBC driver vendors, and different<br>
JDK vendors interpret the use of JAAS for Kerberos propagation there are<br>
a lot of different interpretation of the same spec / APIs!!<br></blockquote><div><br></div><div>JAAS, and especially JAAS in Java EE, is not the universal standard you may think it is. Some parts are interpreted differently, but other parts are just not specified. How to store a username and roles in the "bag of principles" that the Subject is, is particularly notorious. I wrote a post about that subject (no pun) here: <a href="http://arjan-tijms.blogspot.com/2014/02/jaas-in-java-ee-is-not-universal.html">http://arjan-tijms.blogspot.com/2014/02/jaas-in-java-ee-is-not-universal.html</a><br>
<br></div><div>I wonder btw if any of the work done for this WildFly Elytron project (and previous work done for Picketbox/link) could possibly be used for feedback on how to improve the security APIs in Java EE itself. Has this ever been considered?<br>
<br></div><div>Kind regards,<br>Arjan<br></div></div></div></div></div>