Relationship between Payara Platform, MicroProfile and Java EE/Jakarta EE

Cloud & Microservices
No Image

Comments (7)

Post a comment

Your email address will not be published. Required fields are marked *

Payara needs the contact information you provide to us to contact you about our products and services. You may unsubscribe from these communications at any time. For information on how to unsubscribe, as well as our privacy practices and commitment to protecting your privacy, please review our Legal & Privacy Policy.

  1. Volker Kuhn

    Hi Rudy,

    When will JWT officially integrate with Jakarta EE Security in a next release of MicroProfile?

  2. Rudy De Busscher

    Hi Volker,

    The integration needs to be defined by Jakarta EE Security (and MicroProfile JWT Auth has already defined some optional requirements when running in a Java EE server) but I cannot give you an answer on when there is a formal integration into Jakarta EE for the moment. There is no Github issue for this yet, but support for JWT by Security API was already on the table in the past.

    However, you can already use it and you can see an example in this blog https://www.payara.fish/blog/java-ee-security-api-jsr-375/soteria-with-jwt-tokens.

    Regards
    Rudy

  3. Volker Kuhn

    Thanks for the detailed explanation, but I meant, when is MicroProfile going to officially be saying it uses Jakarta EE Security?

    I mean, it’s now using JAX-RS, CDI and JSON. When is MicroProfile saying it’s using JAX-RS, CDI, JSON and Jakarta Security?

  4. Rudy De Busscher

    MicroProfile is never going to use Java EE Security, because it means every MicroProfile implementation also needs to include JASPIC and JACC to name the 2 most important ones. Java EE Security is build on top of those two and thus requires them.

    Regards
    Rudy

  5. Volker Kuhn

    Oh, I thought JASPIC was quite small? Even Tomcat has it 😉

  6. Lars Gielsok

    How deep is the integration of Microprofile into Payara? Is it possible to use a newer Microprofile version with an older payara version by replacing/patching the corresponding app module jar?

  7. Rudy De Busscher

    Hi Lars,

    There is a deep integration of the Payara Server with MicroProfile. So replacing the jar files on an older version will probably fail, especially when the major version is different (MP 1x, 2.x and 3.x).
    Instead, it is recommended to upgrade Payara so that you also benefit from the bug fixings and additional features in the latest version.

    Best regards
    Rudy

Related Posts

Graphic promoting the Jakarta EE Agentic AI Project by Payara Community. The design shows a laptop screen with a central icon of a person wearing headphones and using a laptop, surrounded by sparkles. The background features blue ocean-themed elements with coral and small fish. Logos for Jakarta EE and Payara Community appear at the top. 3 minutes
Community

Announcing the Jakarta Agentic AI Project

Exploring the Future of AI with the Jakarta EE Community At Payara, we’re passionate about pushing the boundaries of […]

JBoss ELS Decoded 5 minutes
Jakarta EE

JBoss ELS Decoded: What Extended Lifecycle Support Really Means for Your Java Applications​

If your Java EE 8 applications run on Red Hat JBoss Enterprise Application Platform (EAP) 7, you can’t afford […]

Graphic with dark blue background featuring an orange shield icon with an exclamation mark inside a triangle, representing security concerns 8 minutes
Jakarta EE

Understanding the Security Issues of Aging Middleware

Middleware runs quietly in the background of most applications, which makes it easy to overlook its lifecycle. In effect, […]