for example JAX-RS application class annotated with @LoginConfig. > only urls defined in the @ApplicationPath should use the JWT Auth method.
Other endpoints, like servlet should use the 'default' method defined in the web.xml. AFAIK, there exist no integration point possible to do this, not even JASPIC. So it needs to be solved by the 'internals' of the Application server. On 9 March 2018 at 12:04, Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > 2018-03-09 12:02 GMT+01:00 Rudy De Busscher <rdebussc...@gmail.com>: > > > No objection but an important remark to make. > > > > it will not be enough to just add this geronimo-jwt-auth artifact to a > > server to have it functional. There will be some server-side integration > > code required (just as we will need for TomEE) > > > > it is not the case for tomee and shouldn't normally if the server > propagates properly its security context. It is not always the case, you > are right, > but for asf servers it should AFAIK, no? > > > > > > This is thus clearly different from other microprofile implementations > like > > geronimo-config. > > > > Just want to mention this as there are already people (outside of this > > community) thinking that such a thing is possible (or should be possible) > > > > Rudy > > > > On 9 March 2018 at 11:49, Romain Manni-Bucau <rmannibu...@gmail.com> > > wrote: > > > > > If there is no other comment, any objection to move it to > > > geronimo-jwt-auth? (let say if not we do it on monday european time) > > > > > > > > > Romain Manni-Bucau > > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > > <https://rmannibucau.metawerx.net/> | Old Blog > > > <http://rmannibucau.wordpress.com> | Github <https://github.com/ > > > rmannibucau> | > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > > > <https://www.packtpub.com/application-development/java- > > > ee-8-high-performance> > > > > > > 2018-03-06 11:11 GMT+01:00 Romain Manni-Bucau <rmannibu...@gmail.com>: > > > > > > > > > > > 2018-03-06 10:24 GMT+01:00 Jean-Louis Monteiro < > > jlmonte...@tomitribe.com > > > >: > > > > > > > >> Hi community, > > > >> > > > >> > > > >> So we now have something close in terms of MP-JWT implementation. > > > >> > > > >> With the playground branch I've been working on (Thanks Romain for > the > > > >> help), we now pass 100% of the TCK (including a missing part in > MP-JWT > > > TCK > > > >> I have eagerly added - see ticket on MP-JWT). > > > >> > > > >> Now the question is how do we proceed? > > > >> Knowing that most of the code is not TomEE specific. > > > >> > > > > > > > > I'd move it to G to a new git repo keeping only the tck exec - a bit > > like > > > > Roberto started with config. I'll be happy to help fixing the small > > > > remaining enhancements to do (jwt parsing based on jsonb/p, config > > etc). > > > > > > > > > > > >> > > > >> Only few things are in the TomcatSecurityService but that can remain > > in > > > >> TomEE because it's not really MP-JWT specific either. > > > >> > > > > > > > > +1, was overdue anyway for our servlet-ejb integration > > > > > > > > > > > >> > > > >> Here is the PR for discussion > > > >> https://github.com/apache/tomee/pull/123 > > > >> > > > >> Cheers > > > >> Jean-Louis > > > >> > > > >> > > > >> -- > > > >> Jean-Louis Monteiro > > > >> http://twitter.com/jlouismonteiro > > > >> http://www.tomitribe.com > > > >> > > > > > > > > > > > > > >
