Rudy De Busscher

JDK17 : Success JDK11 : Failed to Deploy (as expected)

If parts of the spec document are no longer maintained, remove the text and point to the javadoc. Now it is unclear since the spec has some text but is...

I want to get started on this topic since Payara has already an integration of OpenIdConnect with Soteria. You can read more about the supported functionality on this documentation page...

The Soteria PR for OpenId Connect is ready for some months now but no one seems interested to review it to get it included. So I merged the API part...

Since I don't have the time to finish the TCK, the OpenId Connect need to be skipped (and the entire Security API/Soteria 3.0 is not included in Jakarta EE 10)...

I will revert https://github.com/jakartaee/security/commit/7e2ab468a1fbebf33565696e95d01f86ec71427c soon.

But since there is no TCK by next week, we can't include OpenidConnect in the release, simply as that. If you want to ship the small changes that you have...

Is this documented that TCK can be done at a later time? Not that familiar with Jakarta EE specifications but with MicroProfile API, Impl and TCK must be delivered together....

Fine for dropping 'security'. But we should use the `` so that transition becomes easier? EDIT: I'm a sleep, of course I meant enterprise :)

Isn't it easier to just have separate artefacts for CDI lite and CDI full. CDI lite doesn't contain than any reference to EL classes and BeanManager can keep the EL...