Java EE Security API implementation plans for TomEE 8?

in any way? (as I'm also an Apache committer on various projects) Thanks Best regards Rudy De Busscher

Re: The EE8 Roadmap

Great news What are the plans for the Security API? It will also be included in the Web Profile. I can help with the implementation if you like. Best regards Rudy On 17 June 2017 at 21:57, Mark Struberg wrote: > FYI, With help from Romain, Reinhard Sandtner,

Re: [VOTE] Explore creating a reusable JWT Library

> > Primarily what I'd like to do is really nail the public key format > manipulation. I did a huge amount of research in this and would like to > come up with an extremely well tested library that can natively read all > the dominate file formats PKCS 1 & 5 PEM, JWK{S} and has command-line tools

Re: Implementing Microprofile JWT

> > Can we assume Java8 for this attempt? > Oh and more important: Will the integration work based on TomEE7 (would > require Java7) or the upcoming TomEE8? > I'd say we should focus on TomEE8 and Java8 MicroProfile specs are defined in Java 8, so TomEE8 seems the only option. regards Rudy On

Re: MP-JWT progress

share > the > > same impl with tomee to avoid to x2 the effort. however if not desired it > > is fine as well. > > > > It is also important to keep in mind that on tomee side there is *no* > > specific code, only fixes in the propagation which also impact > w

Re: MP-JWT progress

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

Re: MP-JWT progress

I'm not saying we should move TomEE code into Geronimo. If we move the generic stuff for JWT Auth to Geronimo, it will not be enough to have it completely functional. And that should be made clear from the beginning for all potential usages. On 9 March 2018 at 12:20, John D. Ament

Re: MP-JWT progress

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) This is thus clearly different from other microprofile

Re: [RESULT] Explore creating a reusable JWT Library

scussion and a bit > of extra time. > > +1s > Andy Gumbrecht > David Blevins > Ivan Junckes Filho > Jean-Louis Monteiro > Jonathan Gallimore > Thiago Veronezi > > +0 > Rudy De Busscher > > -1s > Mark Struberg > Romain Manni-Bucau > > This was intended

Re: MP.next()

+1 (Non binding) Rudy On 17 April 2018 at 13:12, Roberto Cortez wrote: > > +1On Tuesday, April 17, 2018, 12:11:58 AM GMT+1, Jean-Louis Monteiro < > jlmonte...@tomitribe.com> wrote: > > Hi community, > > Most microprofile requires Java 8. > Is everyone ok if we

Re: [VOTE] Merge Pull Request 123 - MicroProfile JWT support

+1 To merge into TomEE Rudy On 29 March 2018 at 20:19, Ivan Junckes Filho wrote: > Cool, I didn't know I could vote as a contributor. > > I am +1 on this PR to be merged on TomEE. > > On Thu, Mar 29, 2018 at 3:14 PM, Bruno Baptista > wrote: > > > +1

Re: [VOTE] Explore creating a reusable JWT Library

+0 If it needs to be reusable it should also work with other Application Servers (which I don't believe is possible with MP JWT Auth). So First within TomEE and then try it to extract it and make it work elsewhere also. Rudy On 29 March 2018 at 20:21, Ivan Junckes Filho