Planned Security Features for WildFly

This new feature will make it possible to use multiple security realms by sequentially invoking the each of the configured realms until a realm that contains the identity is found. More details can be found here.

If a security realm becomes unavailable for some reason, it will be possible to failover to an alternate realm. More details can be found here.

This feature looks at security integration for RESTEasy clients. More information about this feature can be found here.

Currently, credential store references can be used anywhere in the model where a credential needs to be specified. This feature will make it possible to encrypt other attribute values stored in the management model. More details can be found here.

It will be possible to use SSH authentication via Elytron when using Git to manage and persist your WildFly configuration file. More details are available here.

This feature adds support for the HTTP External authentication mechanism with Elytron, making it possible to authenticate a user based on credentials established externally. More details can be found here.

This feature looks at adding support for BEARER/JWT authentication for EJB invocations over HTTP. More details can be found here.

We recently added support for TLS 1.3 for WildFly when using the JSSE TLS provider with Elytron. This feature will also add support for TLS 1.3 when using the OpenSSL TLS provider with Elytron. More information can be found here.

As an SSLEngine is created, the host and port information is available at the time the engine is requested. This feature looks at making use of this information to dynamically select alternative configurations.