There are notable differences between the JBoss EAP product and the continuous delivery release for JBoss EAP.

Automatic Detection of Keystore Types

The following keystore types are now detected automatically:

The other keystore types must be specified manually.

For more information, see Elytron Subsystem Components Reference in the How to Configure Server Security for JBoss EAP.

Java EE Security API Support in Elytron

The elytron subsystem now supports the Java EE Security API as defined in JSR 375.

The Java EE Security API defines portable plug-in interfaces for authentication and identity stores, and a new injectable-type SecurityContext interface that provides an access point for programmatic security. You can use the built-in implementations of these APIs, or define custom implementations. For details about the specifications, see Java EE Security API Specification.

You can enable the Java EE Security API in the elytron subsystem with minimal configuration steps using the management CLI.

For information on enabling Java EE Security API, see About Java EE Security API in the Development Guide.

Silent BASIC Authentication in Elytron

You can now configure the elytron subsystem to perform a silent BASIC authentication.

When the silent authentication is enabled, a user is not prompted to log in for accessing a web application if the user’s request does not contain an authorization header.

For information about enabling the silent BASIC authentication, see Configure Web Applications to Use Elytron or Legacy Security for Authentication in How to Configure Identity Management.

Utility to Migrate Properties-based Security Realm to Filesystem Realm in Elytron

You can now migrate the legacy properties-based security realm to Elytron’s filesystem-based realm using the filesystem-realm command of the elytron-tool.sh tool.

A filesystem-based realm is a filesystem-based identity store used by Elytron for storing user identities. The filesystem-realm command migrates the properties-realm files to filesystem-realm and also generates commands for adding this realm and a security domain to the elytron subsystem.

For information about the filesystem-realm command, see Migrate to Filesystem-based Security Realm Using the filesystem-realm Command in the Migration Guide for JBoss EAP.

Support for JBoss EAP Subsystem Metrics in Prometheus Format

The Eclipse MicroProfile Metrics functionality is used to provide monitoring data for the JBoss EAP instance. This release enhances the SmallRye Metrics component to provide the JBoss EAP metrics in the Prometheus format.

For information about Eclipse MicroProfile Metrics, see the Eclipse MicroProfile Metrics section in the Configuration Guide.

Display Modules According to Deployment

You can now view a list of modules according to deployment using the list-modules management operation.

For more information about using the list-modules management operation, see the Display Modules by Deployment section in the Development Guide.

Multiple Delivery Groups Support for Message-Driven Beans

A message-driven bean (MDB) can now belong to more than one delivery groups. Message delivery is enabled only when all the delivery groups that an MDB belongs to are active.

For more information, see Delivery Groups in the Developing EJB Applications guide for JBoss EAP.

New Attribute initial-load in the mod_cluster Subsystem

The mod_cluster subsystem now defines a new attribute, initial-load.

The initial-load attribute helps to gradually increase the load value of a newly joined node to avoid overloading it while joining a cluster.

For information on this attribute, see the section ModCluster Subsystem Attributes in the Configuration Guide for JBoss EAP.

Ability to Determine the Primary Singleton Provider

You can now determine the primary singleton provider with the runtime resources that the singleton subsystem exposes for each singleton deployment or service created from a particular singleton policy.

For more information, see Determine the Primary Singleton Service Provider Using the CLI in the Development Guide for JBoss EAP.

Configure JMS Resources for a Remote Artemis-based Broker Using the resourceAdapter Element

You can configure JMS resources for a remote Artemis-based broker, such as Red Hat AMQ 7, using the @JMSConnectionFactoryDefinition annotation or the @JMSDestinationDefinition annotation. The resourceAdapter element defines which resource adapter is used for creating a JMS resource.

For more information, see JMS Resources Configuration for a Remote Artemis-based Broker in the Configuring Messaging book for JBoss EAP.

Configure Global Resources Usage for Messaging Servers

Three new attributes in the address-setting element help you control the global resources usage for messaging servers. For more information, see Configure Global Resource Usage for Messaging Servers in the Configuring Messaging book for JBoss EAP.

Support for some technologies are removed due to the high maintenance cost, low community interest, and better alternative solutions. This release does not introduce any newly unsupported features.

However, the unsupported features listed in the Unsupported Features section of the release notes for JBoss EAP 7.2 also apply to this continuous delivery release for JBoss EAP, unless they are mentioned in the New Features and Enhancements section of this document.

Some features have been deprecated with this release. This means that no enhancements will be made to these features, and they may be removed in the future, usually the next major release.

Red Hat will continue providing full support and bug fixes under our standard support terms and conditions. For more information about the Red Hat support policy, see the Red Hat JBoss Middleware Product Update and Support Policy located on the Red Hat Customer Portal.

For details of which features have been deprecated, see the JBoss Enterprise Application Platform Component Details located on the Red Hat Customer Portal.