One of the users of WildFly 10.0.0.Final reports that when he configured the truststore as follows:

<truststore provider="jks" path="server.truststore" relative-to="jboss.server.config.dir" keystore-password="#######"/>

Notice the value for provider - it's lower case jks. Apparently this causes issues and the truststore doesn't work. It works when the value is set to JKS instead.

Looking at the code in SecurityRealmAddHandler it does a case sensitive check on the value to see if it's a JKS provider and if it is, only then does it use the configured keystore relative path. Otherwise, it just ignores the keystore relative path and leads to hard to debug SSL issues.

I think it would be better to do a case insensitive check to see if JKS is the configured keystore provider.

The relevant forum thread discussion is here https://developer.jboss.org/message/958142#958142