[JBoss JIRA] Created: (AS7-1341) Link to console on startup page fails when running in EC2/limited network with any-address
8:28 a.m.
Link to console on startup page fails when running in EC2/limited network with
any-address
------------------------------------------------------------------------------------------
Key: AS7-1341
URL: https://issues.jboss.org/browse/AS7-1341
Project: Application Server 7
Issue Type: Bug
Reporter: Max Rydahl Andersen
Not sure if this is supposed to work but seems it could be detected and then handled
better.
Started AS7 on an EC2 instance with:
<interfaces>
<interface name="management">
<any-address/>
</interface>
<interface name="public">
<any-address/>
</interface>
</interfaces>
to have it actually be available from the outside.
Then going to http://<echostname>:8080 the http://<echohostname>:8080/console
link on the frontpage redirects to http://0.0.0.0:9990/console
which doesn't resolve to anything anywhere ;)
I would expect an error page as when the management console is not available at all or at
least use the same url as the incoming request.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:04 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (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...
]
Andre Dietisheim edited comment on AS7-1341 at 7/19/11 10:03 AM:
-----------------------------------------------------------------
The management port seems configured correctly:
{code}
<management-interfaces>
<native-interface interface="management" port="9999"/>
<http-interface interface="management" port="9990"/>
</management-interfaces>
{code}
Nevertheless, if I try to substitute the http://0.0.0.0:9990 by the proper ec2 address:
http://ec2-107-20-15-112.compute-1.amazonaws.com:9990/console
I get redirected to http://ec2-107-20-15-112.compute-1.amazonaws.com/:9990/console which
is not valid either.
was (Author: adietish):
The management port seems configured correctly:
{code}
<management-interfaces>
<native-interface interface="management" port="9999"/>
<http-interface interface="management" port="9990"/>
</management-interfaces>
{code}
Nevertheless, if I try to substitute the 0.0.0.0:9990 by the proper ec2 address:
ec2-107-20-15-112.compute-1.amazonaws.com:9990/console
I get redirected to http://ec2-107-20-15-112.compute-1.amazonaws.com/:9990/console which
is not valid either.
Link to console on startup page fails when running in EC2/limited
network with any-address
------------------------------------------------------------------------------------------
Key: AS7-1341
URL: https://issues.jboss.org/browse/AS7-1341
Project: Application Server 7
Issue Type: Bug
Reporter: Max Rydahl Andersen
Not sure if this is supposed to work but seems it could be detected and then handled
better.
Started AS7 on an EC2 instance with:
<interfaces>
<interface name="management">
<any-address/>
</interface>
<interface name="public">
<any-address/>
</interface>
</interfaces>
to have it actually be available from the outside.
Then going to http://<echostname>:8080 the http://<echohostname>:8080/console
link on the frontpage redirects to http://0.0.0.0:9990/console
which doesn't resolve to anything anywhere ;)
I would expect an error page as when the management console is not available at all or at
least use the same url as the incoming request.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:04 a.m.
New subject: [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...
]
Andre Dietisheim commented on AS7-1341:
---------------------------------------
The management port seems configured correctly:
{xml}
<management-interfaces>
<native-interface interface="management" port="9999"/>
<http-interface interface="management" port="9990"/>
</management-interfaces>
{xml}
Nevertheless, if I try to substitute the 0.0.0.0:9990 by the proper ec2 address:
ec2-107-20-15-112.compute-1.amazonaws.com:9990/console
I get redirected to http://ec2-107-20-15-112.compute-1.amazonaws.com/:9990/console which
is not valid either.
Link to console on startup page fails when running in EC2/limited
network with any-address
------------------------------------------------------------------------------------------
Key: AS7-1341
URL: https://issues.jboss.org/browse/AS7-1341
Project: Application Server 7
Issue Type: Bug
Reporter: Max Rydahl Andersen
Not sure if this is supposed to work but seems it could be detected and then handled
better.
Started AS7 on an EC2 instance with:
<interfaces>
<interface name="management">
<any-address/>
</interface>
<interface name="public">
<any-address/>
</interface>
</interfaces>
to have it actually be available from the outside.
Then going to http://<echostname>:8080 the http://<echohostname>:8080/console
link on the frontpage redirects to http://0.0.0.0:9990/console
which doesn't resolve to anything anywhere ;)
I would expect an error page as when the management console is not available at all or at
least use the same url as the incoming request.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:04 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (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...
]
Andre Dietisheim edited comment on AS7-1341 at 7/19/11 10:02 AM:
-----------------------------------------------------------------
The management port seems configured correctly:
{code}
<management-interfaces>
<native-interface interface="management" port="9999"/>
<http-interface interface="management" port="9990"/>
</management-interfaces>
{code}
Nevertheless, if I try to substitute the 0.0.0.0:9990 by the proper ec2 address:
ec2-107-20-15-112.compute-1.amazonaws.com:9990/console
I get redirected to http://ec2-107-20-15-112.compute-1.amazonaws.com/:9990/console which
is not valid either.
was (Author: adietish):
The management port seems configured correctly:
{xml}
<management-interfaces>
<native-interface interface="management" port="9999"/>
<http-interface interface="management" port="9990"/>
</management-interfaces>
{xml}
Nevertheless, if I try to substitute the 0.0.0.0:9990 by the proper ec2 address:
ec2-107-20-15-112.compute-1.amazonaws.com:9990/console
I get redirected to http://ec2-107-20-15-112.compute-1.amazonaws.com/:9990/console which
is not valid either.
Link to console on startup page fails when running in EC2/limited
network with any-address
------------------------------------------------------------------------------------------
Key: AS7-1341
URL: https://issues.jboss.org/browse/AS7-1341
Project: Application Server 7
Issue Type: Bug
Reporter: Max Rydahl Andersen
Not sure if this is supposed to work but seems it could be detected and then handled
better.
Started AS7 on an EC2 instance with:
<interfaces>
<interface name="management">
<any-address/>
</interface>
<interface name="public">
<any-address/>
</interface>
</interfaces>
to have it actually be available from the outside.
Then going to http://<echostname>:8080 the http://<echohostname>:8080/console
link on the frontpage redirects to http://0.0.0.0:9990/console
which doesn't resolve to anything anywhere ;)
I would expect an error page as when the management console is not available at all or at
least use the same url as the incoming request.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:49 a.m.
New subject: [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...
]
David Lloyd commented on AS7-1341:
----------------------------------
Using the literal IP address from an {{<interface>}} tag, or using the localAddress
of a bound socket, to construct a public URL is always incorrect, at least when said
address resolves to {{0.0.0.0}} or {{::}}. I thought we had a public interface detection
mechanism?
Link to console on startup page fails when running in EC2/limited
network with any-address
------------------------------------------------------------------------------------------
Key: AS7-1341
URL: https://issues.jboss.org/browse/AS7-1341
Project: Application Server 7
Issue Type: Bug
Reporter: Max Rydahl Andersen
Not sure if this is supposed to work but seems it could be detected and then handled
better.
Started AS7 on an EC2 instance with:
<interfaces>
<interface name="management">
<any-address/>
</interface>
<interface name="public">
<any-address/>
</interface>
</interfaces>
to have it actually be available from the outside.
Then going to http://<echostname>:8080 the http://<echohostname>:8080/console
link on the frontpage redirects to http://0.0.0.0:9990/console
which doesn't resolve to anything anywhere ;)
I would expect an error page as when the management console is not available at all or at
least use the same url as the incoming request.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:34 p.m.
New subject: [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...
]
Tom Manning commented on AS7-1341:
----------------------------------
What's the correct way to do this?
Link to console on startup page fails when running in EC2/limited
network with any-address
------------------------------------------------------------------------------------------
Key: AS7-1341
URL: https://issues.jboss.org/browse/AS7-1341
Project: Application Server 7
Issue Type: Bug
Reporter: Max Rydahl Andersen
Not sure if this is supposed to work but seems it could be detected and then handled
better.
Started AS7 on an EC2 instance with:
<interfaces>
<interface name="management">
<any-address/>
</interface>
<interface name="public">
<any-address/>
</interface>
</interfaces>
to have it actually be available from the outside.
Then going to http://<echostname>:8080 the http://<echohostname>:8080/console
link on the frontpage redirects to http://0.0.0.0:9990/console
which doesn't resolve to anything anywhere ;)
I would expect an error page as when the management console is not available at all or at
least use the same url as the incoming request.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:52 a.m.
New subject: [JBoss JIRA] Assigned: (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 reassigned AS7-1341:
-------------------------------------
Assignee: Darran Lofthouse
Link to console on startup page fails when running in EC2/limited
network with any-address
------------------------------------------------------------------------------------------
Key: AS7-1341
URL: https://issues.jboss.org/browse/AS7-1341
Project: Application Server 7
Issue Type: Bug
Reporter: Max Rydahl Andersen
Assignee: Darran Lofthouse
Not sure if this is supposed to work but seems it could be detected and then handled
better.
Started AS7 on an EC2 instance with:
<interfaces>
<interface name="management">
<any-address/>
</interface>
<interface name="public">
<any-address/>
</interface>
</interfaces>
to have it actually be available from the outside.
Then going to http://<echostname>:8080 the http://<echohostname>:8080/console
link on the frontpage redirects to http://0.0.0.0:9990/console
which doesn't resolve to anything anywhere ;)
I would expect an error page as when the management console is not available at all or at
least use the same url as the incoming request.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:46 a.m.
New subject: [JBoss JIRA] Updated: (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 updated AS7-1341:
----------------------------------
Fix Version/s: 7.1.0.Alpha1
Component/s: Domain Management
Web
Link to console on startup page fails when running in EC2/limited
network with any-address
------------------------------------------------------------------------------------------
Key: AS7-1341
URL: https://issues.jboss.org/browse/AS7-1341
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, Web
Reporter: Max Rydahl Andersen
Assignee: Darran Lofthouse
Fix For: 7.1.0.Alpha1
Not sure if this is supposed to work but seems it could be detected and then handled
better.
Started AS7 on an EC2 instance with:
<interfaces>
<interface name="management">
<any-address/>
</interface>
<interface name="public">
<any-address/>
</interface>
</interfaces>
to have it actually be available from the outside.
Then going to http://<echostname>:8080 the http://<echohostname>:8080/console
link on the frontpage redirects to http://0.0.0.0:9990/console
which doesn't resolve to anything anywhere ;)
I would expect an error page as when the management console is not available at all or at
least use the same url as the incoming request.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:50 p.m.
New subject: [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.
Link to console on startup page fails when running in EC2/limited
network with any-address
------------------------------------------------------------------------------------------
Key: AS7-1341
URL: https://issues.jboss.org/browse/AS7-1341
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, Web
Reporter: Max Rydahl Andersen
Assignee: Darran Lofthouse
Fix For: 7.1.0.Alpha1
Not sure if this is supposed to work but seems it could be detected and then handled
better.
Started AS7 on an EC2 instance with:
<interfaces>
<interface name="management">
<any-address/>
</interface>
<interface name="public">
<any-address/>
</interface>
</interfaces>
to have it actually be available from the outside.
Then going to http://<echostname>:8080 the http://<echohostname>:8080/console
link on the frontpage redirects to http://0.0.0.0:9990/console
which doesn't resolve to anything anywhere ;)
I would expect an error page as when the management console is not available at all or at
least use the same url as the incoming request.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:01 a.m.
New subject: [JBoss JIRA] Updated: (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 updated AS7-1341:
----------------------------------
Fix Version/s: 7.0.2.Final
(was: 7.1.0.Alpha1)
Link to console on startup page fails when running in EC2/limited
network with any-address
------------------------------------------------------------------------------------------
Key: AS7-1341
URL: https://issues.jboss.org/browse/AS7-1341
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, Web
Reporter: Max Rydahl Andersen
Assignee: Darran Lofthouse
Fix For: 7.0.2.Final
Not sure if this is supposed to work but seems it could be detected and then handled
better.
Started AS7 on an EC2 instance with:
<interfaces>
<interface name="management">
<any-address/>
</interface>
<interface name="public">
<any-address/>
</interface>
</interfaces>
to have it actually be available from the outside.
Then going to http://<echostname>:8080 the http://<echohostname>:8080/console
link on the frontpage redirects to http://0.0.0.0:9990/console
which doesn't resolve to anything anywhere ;)
I would expect an error page as when the management console is not available at all or at
least use the same url as the incoming request.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4894
days inactive
4924
days old
9 comments
5 participants
participants (5)
-
Andre Dietisheim (JIRA) -
Darran Lofthouse (JIRA)
-
David Lloyd (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Tom Manning (JIRA)