-
1. Re: JBossAs 7.1.1 Final apache proxy for admin console on port 9990 does not work.
wdfink Mar 24, 2012 8:39 AM (in response to hurzeler)What bind addresses do you use.
I suppose that localhost is given to the client and that can't work.
Do you bind the 'public' interface against a IP address with -b or configuration and the management not?
-
2. Re: JBossAs 7.1.1 Final apache proxy for admin console on port 9990 does not work.
hurzeler Mar 24, 2012 11:05 AM (in response to wdfink)I am not using any -b (server bind address) and have the default interface definitions:
<interfaces>
<interface name="management">
<inet-address value="${jboss.bind.address.management:127.0.0.1}"/>
</interface>
<interface name="public">
<inet-address value="${jboss.bind.address:127.0.0.1}"/>
</interface>
<interface name="unsecure">
<inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/>
</interface>
</interfaces>
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
<socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>
<socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>
<socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/>
<socket-binding name="ajp" port="8009"/>
<socket-binding name="http" port="8080"/>
<socket-binding name="https" port="8443"/>
<socket-binding name="osgi-http" interface="management" port="8090"/>
<socket-binding name="remoting" port="4447"/>
<socket-binding name="txn-recovery-environment" port="4712"/>
<socket-binding name="txn-status-manager" port="4713"/>
<outbound-socket-binding name="mail-smtp">
<remote-destination host="localhost" port="25"/>
</outbound-socket-binding>
</socket-binding-group> -
3. Re: JBossAs 7.1.1 Final apache proxy for admin console on port 9990 does not work.
hurzeler Mar 24, 2012 11:06 AM (in response to hurzeler)BTW there is no error in the server console/log (server.xml), apache access/error log.
-
4. Re: JBossAs 7.1.1 Final apache proxy for admin console on port 9990 does not work.
heiko.braun Mar 27, 2012 6:43 AM (in response to hurzeler)You would need to check the browser javascript log. Could be a SOP problem (same origin policy).
-
5. Re: JBossAs 7.1.1 Final apache proxy for admin console on port 9990 does not work.
hurzeler Mar 28, 2012 1:52 AM (in response to heiko.braun)By doing a bit more research I found that this is related to: https://issues.jboss.org/browse/AS7-1856.
I am just wondering if there is a way where we can still set the admin console up through an Apache proxy or is it just not possible due to the double Authentication issue (BASIC HTTP).
BTW the browser logs this error;
- OPTIONS https://somedomain.com.au:80/management Resource failed to load 1FBC5F0CFA0986D58F13AB842DD04F8E.cache.html:7250
- 2012-03-28 16:49:01,932 [ERROR] Authentication required. Could not execute { "operation" => "read-attribute", "name" => "process-type", "address" => [] } 1FBC5F0CFA0986D58F13AB842DD04F8E.cache.html:681
- 2012-03-28 16:49:01,939 [ERROR] Failed to execute org.jboss.as.console.client.core.bootstrap.ExecutionMode 1FBC5F0CFA0986D58F13AB842DD04F8E.cache.html:681
-
6. Re: JBossAs 7.1.1 Final apache proxy for admin console on port 9990 does not work.
heiko.braun Mar 28, 2012 4:18 AM (in response to hurzeler)Can you confirm that this statement applies to you:
"If the '/management' context is going to be proxied through Apache then Apache should not secure this context at the same time as this same context is secured within AS itself. If the security is disabled on AS7 for the HTTP interface then a secured Apache instance can proxy the requests but in the future this would cause a loss of the ACL / authorization support being added shortly."
(Taken from https://issues.jboss.org/browse/AS7-1856)
-
7. Re: JBossAs 7.1.1 Final apache proxy for admin console on port 9990 does not work.
dlofthouse Mar 28, 2012 5:11 AM (in response to heiko.braun)Also to add to the comment from Heiko - as in the comment you can disable the security on the http interface but that will then mean that ANYTHING that can get a direct connection to port 9990 of your AS server will then have full access to do anything they like to that installation.
-
8. Re: JBossAs 7.1.1 Final apache proxy for admin console on port 9990 does not work.
jsightler Apr 13, 2012 3:11 PM (in response to hurzeler)I also see this issue. The logs look like this for me as well:
- OPTIONS https://somedomain:80/management Resource failed to load 1FBC5F0CFA0986D58F13AB842DD04F8E.cache.html:7250
- 2012-03-28 16:49:01,932 [ERROR] Authentication required. Could not execute { "operation" => "read-attribute", "name" => "process-type", "address" => [] } 1FBC5F0CFA0986D58F13AB842DD04F8E.cache.html:681
- 2012-03-28 16:49:01,939 [ERROR] Failed to execute org.jboss.as.console.client.core.bootstrap.ExecutionMode 1FBC5F0CFA0986D58F13AB842DD04F8E.cache.html:681
For some reason, the requests to the /management are (correctly) using https, but (incorrectly) using port 80 instead of port 443. What could cause the server to use the wrong port for this load?
-
9. Re: JBossAs 7.1.1 Final apache proxy for admin console on port 9990 does not work.
jsightler Apr 13, 2012 3:53 PM (in response to hurzeler)This is actually a bug. The port isn't handled correctly:
-
10. Re: JBossAs 7.1.1 Final apache proxy for admin console on port 9990 does not work.
heiko.braun Apr 16, 2012 4:09 AM (in response to jsightler)tnx j. good catch. i'll make sure it gets included in the next release: