2) If a request is received for which a matching <security-constraint> requires SSL transport, undertow will automatically redirect the request to the socket binding port specified here. In the case it will redirect to "https"

Thanks for the prompt response. However, I can't locate any details on how/where to implement your suggestion. Would you point me to documentation that describes how to do this, or if possible, could you explain the details? Is this added to standalone.xml? The statements you listed aren't in the <...> <...> XML format I am used to seeing so I don't understand what is to be added (to what).

Thank you very much for providing the link to your blog posting. That led me to finally figuring out what was going wrong. I now have the console connecting over TLS and also a straight HTTP console connection times out which is exactly what I want.

So that any one else reading this incident is made aware, in WildFly 10 the standalone.XML file places the HTTPS entries in the ApplicationRealm! What I mean is that when I examined the default standalone.XML I discovered the following (note the ApplicationRealm in the following):

The ApplicationRealm is for end user applications to access the regular 443 port. The ManagementRealm is for users to manage the Wildfly itself, that is the distinction. However, you are free to create other realms to manage them.