On 16/10/2015 11:44, Rémy Maucherat wrote: <snip/>
> What's not clear to me at this point is if jaspic should replace the > current "classic" auth methods. For example, the supposed benefit of jaspic > is that it makes container auth not proprietary, but looking at the code > that is there it sounds still quite proprietary in practice and almost > impossible to use from webapps. So what's the point exactly ? The main benefit for me is that once Tomcat implements JASPIC, there are a handful of 3rd party modules that users will then be able to use just by adding the lib to Tomcat. It also provides a standard API for users to work against if they want to develop their own custom modules. Those modules would then be usable with any container that implements JASPIC. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
