[wildfly-dev] Enhancing the HTTP Management Interface Configuration - WFLY-2635

[Brian Stansberry]

I agree.

Sent from my iPhone

> On May 2, 2014, at 9:51 PM, "Jason T. Greene" <jgreene at redhat.com> wrote:
> 
> I don't believe we want to require SSO out of the box. That would be too much infrastructure for a simple setup.
> 
>> On May 2, 2014, at 2:27 AM, Heiko Braun <hbraun at redhat.com> wrote:
>> 
>> If i understand it correctly, the new auth method you mention has no relation to sso (the brno design decisions, right?). Maybe its worth exploring the commonalities and differences to see if we can move to keycloak right away? Assuming that we dont wont two pssible authentication options. The way i see it keycloak sso would be a replacement for the new auth method you desribe, right?
>> 
>> Heiko
>> 
>> 
>> 
>>> Am 01.05.2014 um 20:05 schrieb Darran Lofthouse <darran.lofthouse at jboss.com>:
>>> 
>>> I will send round some design ideas / config examples next week but if 
>>> there are any additional demands on the HTTP management interface in 
>>> addition to a path to enabling alternative distribution approaches and 
>>> the enablement of SSO not is the time to speak up ;-)
>> 
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
> 
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev