[wildfly-dev] access to mgmt api/services

Jason Greene jason.greene at redhat.com
Wed Feb 5 11:23:20 EST 2014


On Feb 5, 2014, at 9:23 AM, Bill Burke <bburke at redhat.com> wrote:

> 
> 
> On 1/27/2014 9:48 PM, Bill Burke wrote:
>>>> This is for bootstrap purposes for getting a Wildfly instance to join a
>>>> Keycloak federation.  I want the Keycloak server to be able to send
>>>> realm configuration information to a Wildfly instance (over HTTP(S))
>>>> that is joining the federation and have that instance store this
>>>> information within a subsystem.  So, it is a one off service that
>>>> happens after boot and may even be disabled afterwards.
>>>> 
>>>> 
>>> 
>>> This can't be done using the HTTP management interface?
>>> 
>> 
>> After thinking a bit, I guess it could just use the HTTP mgmt intf.
>> Thanks for your patience helping me work this out.
>> 
> 
> Ok, found a reason why just using the HTTP mgmt interface isn't good enough:
> 
> Openshift disables admin port :(  You can set up port forwarding to be 
> able to access it, but, still kinda sucks for usability, which is what 
> I'm trying to optimize.

We have been planning to provide an OTB single port config for open shift, but it fell through the cracks. IIRC all of the hooks are there for it. I’ll put that on my TODO after we cut 8 Final, perhaps bundle it in 8.0.1.

--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat




More information about the wildfly-dev mailing list