Skip to main content

[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 Tue, Nov 8, 2022 at 9:55 PM David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
MP JWT does define bindings for EJB, Servlets, JACC, JASPIC, etc.

True, although essentially spelling out everything is unnecessary if one just says that MP JWT in a Jakarta EE environment is/exposes itself as an Jakarta Security Authentication Mechanism. All those other things then follow from that. Specifically this authentication mechanism bit is missing there. I do see identity store being mentioned, and perhaps it comes from the confusion that many people have between the concept of an authentication mechanism (FORM, BASIC, etc) and an identity store (DB, LDAP, FILE, etc). 

 
# Procedural

In CN4J we did agree to some technical principles.  One of them is that duplication should be avoided.

That is basically a good thing. The problem here is a little that MP JWT in a sense "hi-jacked" the JWT authentication mechanism from underneath Jakarta Security. Of course it's not that black and white in practice, and there were many valid arguments for MP to introduce JWT in the way it did. But the matter of fact remains that Jakarta Security planned for a number of authentication mechanisms that went beyond the ones provided by servlet, such as Open ID Connect (OAuth) and JWT. 

These didn't make it into 1.0, and because of the move to Eclipse the new features effort was stalled for years. In that timeframe JWT was introduced in MP. Currently Jakarta EE is open for new features again, but it finds some features are now "controversial" only because MP implemented them in the meantime. Again, there was no malintent (I was even part of the original MP JWT team then), but it's an unfortunate situation.

Kind regards,
Arjan Tijms



 
 

 - https://docs.google.com/presentation/d/1i7hBzjXtApAUQDopPopLNG0yuwLXBLiSAFKr1_jhFlQ/edit?pli=1#slide=id.ge89d7772e8_0_9

Copying MP JWT would violate the principles we agreed on.  The process for getting agreement between the two groups for a move is basically:

 - Create a proposal and get a member of each WG to sponsor (endorse) it
 - Once sponsored, both WGs independently vote to approve it
 - If both WGs agree, it can move forward


Hope this helps.


-David

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

Back to the top