[jboss-jira] [JBoss JIRA] Commented: (AS7-1341) Link to console on startup page fails when running in EC2/limited network with any-address

[ https://issues.jboss.org/browse/AS7-1341?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on AS7-1341: --------------------------------------- Reviewing this issue further the scenarios where we should be able to perform this redirect are limited, for that reason I will reduce the scope of where redirects occur. Firstly it is intentional that the http interface is using it's own interface definition and port so that access to the admin console is not automatically made available to users that can access the connector exposed by JBoss Web. The HTTP management service contains a NetworkInterfaceBinding that contains all the network interfaces identified as valid for the interface definition, the approach I will take is to identify the address used for the incoming address and verify that the address is assigned to one of those network interfaces, if so I will then use the host name from the original request to form the redirect. Using the host name is also important for the https redirects as this forms a part of verifying the certificate from the server so switching to an IP address would fail that verification. Where the incoming address does not match any of the network interfaces an information / error page will be displayed instead - in that scenario we do not even have sufficient information to identify if the end user can even reach the admin console so we will just avoid leaking internal configuration details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira