This content has been marked as final.
Show 1 reply
-
1. Re: Wildfly Management Console behind AWS ALB
ceharris Sep 7, 2018 3:50 PM (in response to ceharris)Of course, after posting... figured out that it was a CORS issue. Adding an allowed origin for the network that sits in between the load balancer and Wildfly solves this issue. Specifically:
/core-service=management/management-interface=http-interface:list-add(\
name=allowed-origins, value=${env.WILDFLY_MGMT_ALLOWED_ORIGIN})
I'm using the WILDFLY_MGMT_ALLOWED_ORIGIN environment variable to keep the specific address out of the Wildfly configuration as it is apt to change.
Hopefully this will help someone else.