----- Original Message -----
From: "Bill Burke" <bburke(a)redhat.com>
Sent: Monday, 3 November, 2014 2:06:33 PM
Subject: Re: [keycloak-dev] Next steps
I think this will require a Jetty adapter (for HTTP based services) and
a JAAS plugin (or whatever they use to delegate to backend security
store for an SPI) for non-http services.
That was my assumption as well. Not sure how we can deal with login through the Fuse CLI,
maybe that'll just have to be direct access grant?
On 11/3/2014 7:46 AM, Stian Thorgersen wrote:
> Just to clarify next steps is BRMS and Fuse adapters. I assume we're aiming
> at securing the management consoles, services as well as end-user
> For Fuse this would include:
> * Hawtio console
> * Fuse CLI
> * Camel?
> * ActiveMQ?
> Once Fuse is completed we could also look at securing Fabric8.
> I've made some notes here
> As I'm away on PTO Friday and the following week Marek will look at Fuse
> adapter, while I'll help out if it makes sense.
> keycloak-dev mailing list
JBoss, a division of Red Hat
keycloak-dev mailing list