| Re: [microprofile-wg] MicroProfile and Jakarta EE |
I spent some time thinking about the technical solutions on how to get Jakarta Security to use MicroProfile JWT without forking. I think it is feasible. I prepare to chair a call between Jakarta Security and the MicroProfile JWT teams to define the right scope. A doodle poll will be available for people to register soon.ThanksEmilyOn Wed, Mar 1, 2023 at 7:28 PM Reza Rahman <reza_rahman@xxxxxxxxx> wrote:_______________________________________________As discussed, if the substantive concern is around MicroProfile JWT and Jakarta Security, then the next step is to facilitate a direct, technically focused conversation between the leads/committers of MicroProfile JWT (probably including David) and Jakarta Security (probably including Arjan). Microsoft is more than willing to facilitate such a conversation and believes there is much room for productive compromise towards advancing the best interests of end users, both technology sets, and the broader ecosystem. It is best to defer other potentially problematic/contentious actions before this conversation can properly take place.
As previously stated, Microsoft would be forced to regrettably vote -1 without further comment to the current resolution as proposed.
I sincerity hope this helps us move forward in a productive direction.
On 3/1/2023 2:08 PM, John Clingan wrote:
Based on relatively recent discussions, Red Hat is concerned that specifications defined in MicroProfile may get forked into Jakarta EE. We have been having discussions on this topic for a month or so, and I took the action item of having the discussion on the microprofile-wg email alias.. The discussion was generated due to Red Hat’s proposed MicroProfile ballot (draft) verbiage:
”Resolved, the MicroProfile Steering Committee agrees to utilize Jakarta EE specifications in whole or part by reference and not by forking a Jakarta EE specification"
However, if we were to vote, then we would desire a reciprocal Jakarta EE Working Group, similar to the following:
”Resolved, the Jakarta EE Steering Committee agrees to utilize MicroProfile specifications in whole or part by reference and not by forking a MicroProfile specification"
To summarize where we are at with the discussion:
There is already some layering and/or referencing in place - MicroProfile layers on Jakarta specs in whole (JAX-RS, CDI, etc) and in part (JWT layers on some Java Security APIs like isCallerInRole() ).
We would like Jakarta EE to take a similar approach, and reference MicroProfile APIs instead of forking
We would like to gain consensus within MicroProfile, and then have the conversation with the Jakarta EE working group (perhaps via CN4J).
Status (feel free to correct):
Red Hat supports this proposal
Tomitribe supports this proposal (in the context of Intellectual Property)
Microsoft feels that if MP/Jakarta can attain technical alignment (ex: API by reference) and maintain vendor neutrality, then it is a step towards supporting this proposal
The remaining question is, is this sufficient context for us to engage Jakarta EE to attain alignment, or are there any outstanding issues to address before engaging Jakarta EE Working Group?
_______________________________________________ microprofile-wg mailing list microprofile-wg@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/microprofile-wg
microprofile-wg mailing list
microprofile-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/microprofile-wg
--Thanks
Emily