[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakartaee-platform-dev] Moving MicroProfile JWT to Jakarta Security?
|
Hi,
On Saturday, November 5, 2022, Rudy De Busscher <
rdebusscher@xxxxxxxxx> wrote:
Integration into Jakarta Security is not a valid approach as that one has dependencies on Servlet and JASPIC which we don't have for MicroProfile.
Integration into Jakarta Security itself is valid, as Jakarta EE and Jakarta Security have no issues with Servlet and the authentication Servlet container profile. So we can copy JWT to Jakarta Security without any problems.
But I think you mean something else here?
Kind regards,
Arjan Tijms
Moving the Spec to Jakarta like what is done now for Config is a valid approach and recommended in my opinion and this seems logical for most developers (especially now that we have the Core profile that is created specifically to bring over the MicroProfile specs)
Regards
Rudy
+1 on what David said!
We should not spend time copying and pasting from one spec to another as our end users are using both technologies together. Having two similar things in both places does not bring any additional value but confusion. We should focus our limited resources on the area that MicroProfile and Jakarta EE have not covered. Jakarta EE and MicroProfile should work together as a unit to gain more popularity and become more and more successful.
Thanks
Emily
We could also go work on MP JWT and include that in our implementations?
Hi,
In Jakarta Security we had long ago planned to include a JWT authentication mechanism. Some prototypes from around 2016 are still testimony to that.
Meanwhile, MicroProfile has specified JWT, and a couple of implementations of it (such as Payara, OmniFaces and SmallRye) are internally based on Jakarta Security.
We have discussed moving or copying MP specs to EE before, but nothing concrete has been established. Therefore I wonder how to proceed here.
Do we copy over the MP JWT spec to a section in Jakarta Security and somehow keep them in sync?
Or do we reference the MP JWT spec from the Jakarta Security spec with text like: a compliant implementation should provide an authentication mechanism that behaves exactly like MP JWT with the following differences…
Or something else?
Thoughts?
Kind regards,
Arjan Tijms
______________________________
_________________
es-dev mailing list
es-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/es-dev
jakartaee-platform-dev mailing list
jakartaee-platform-dev@eclipse.org
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
--
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@eclipse.org
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
