[Hawkular-dev] Tenancy model (was Re: Do not depend on Keycloak anymore)

Heiko W.Rupp hrupp at redhat.com
Mon Apr 18 14:06:02 EDT 2016


On 18 Apr 2016, at 16:57, Juraci Paixão Kröhling wrote:

> On 15.04.2016 15:14, Juraci Paixão Kröhling wrote:
>> On 15.04.2016 14:43, Heiko W.Rupp wrote:
>>> Yes, that *may* require a change. Or not if we e.g. have
>>> - accounts-keycloak
>>> - accounts-jaas
>>> where the latter does the mapping as a jaas provider/plugin.
>
> I'm still not convinced why we would need two modules. If we assume that
> Hawkular is similar to a database, in the sense that end users have no
> access to it, then there would be no need for any advanced feature from
> Keycloak. Plain JAAS would suffice.

We have 2 different use cases:

- Hawkular as we know it. Including KC, Multi-tenancy and the full enchilada
- Hawkular that works like a database for users like ManageIQ, that only need
 this one technical user to talk to Hawkular.


More information about the hawkular-dev mailing list