Today WildFly does not support server-side SNI, i.e. if a client requests a specific servername using the SNI extension of TLS, WildFly always responds with the default certificate.

The following two PRs add support for server side SNI to WildFly, now WildFly supports a keystore with multiple certificates, and will response with the correct certificate when the client makes use of the SNI extension to indicate a specific servername during the request.

https://github.com/wildfly-security/wildfly-openssl-natives/pull/7

https://github.com/wildfly-security/wildfly-openssl/pull/99

Change in wildfly-openssl depend on changes in wildfly-openssl-natives.