Posts tagged Security
This is an updated blog of the original which was published in May 2016
Payara Server provides the Health Check Service for automatic self-monitoring in order to detect future problems as soon as possible. When enabled, the Health Check Service periodically checks some low level metrics. Whenever it detects that a threshold is not met, it triggers alert notifications that allow to detect undesired behavior and predict possible failures. All of these automatic checks are very lightweight and run with a negligible impact on performance.
If your business processes branded credit card data (such as Visa, MasterCard, American Express, and Discover), you must comply with the Payment Card Industry Data Security Standard (PCI DSS). The requirements were developed and are maintained by the Payment Card Industry Security Standards to reduce credit card fraud and implement increased controls around cardholder information. For companies using the Payara Platform, having a Payara Enterprise subscription helps you maintain compliance.
Java EE Security API is one of the new APIs in Java EE 8. With Java EE currently being transferred and rebranded to Jakarta EE, this API will soon be rebranded to Jakarta Security, which is the term we'll use in this article. Jakarta Security is part of the Jakarta APIs, included and active in the Payara Platform by default with no configuration required in order to use it. With some effort, Jakarta Security can be used with Tomcat, as well.
Java EE 8 introduced a new API called the Java EE Security API (see JSR 375) or "EE Security" in short.
This new API, perhaps unsurprisingly given its name, deals with security in Java EE. Security in Java EE is obviously not a new thing though, and in various ways it has been part of the platform since its inception.
So what is exactly the difference between EE Security and the existing security facilities in Java EE? In this article we'll take a look at that exact question.