An implementation of MP JWT cannot be referenced by Jakarta Security as mentioned by several on this thread, at most an implementation in theory also Soteria or a container that uses the Soteria implementation could also use MP JWT and most likely those will always have multiple different versions of the Underlying dependencies causing a risk factor for the application if the older ones get used in the Soteria 4+ context and vice versa.
Gesendet von Mail für Windows
Right, Jakarta Security, and yes, an implementation of MP JWT would be needed if referenced by Jakarta Security. That is what we would want as opposed to having two implementations in our containers that support both.
It is an externally developed specification that describes a simple API for JWTs and integrations with CDI, not an implementation project.
List your reasons why it cannot be consumed as such and extended in Java Security.
I'm not sure I follow. It's either in the Jakarta Security (not Java Security) spec or it's not. If it's not, users would have to add some implementation of MP JWT to their .war files. At that point it's not much different from adding say DeltaSpike, PrimeFaces, etc to a .war.
But maybe you meant something else there?
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
