Yeah, I've talked with Bolek as well and we discussed about focusing on JPA (which I
was already using) for now, but still provide a SPI for future implementations.
From a SPI perspective, I did something very simple without KC's
org.keycloak.provider.Spi. The main reason for this decision is that Spis in KC are not
loaded when defined within a custom provider and I'm trying to minimize changes in KC
itself.
However, if necessary, I can provide some minor changes to make that happen. So Spis can
also be loaded from custom providers.
Thanks.
----- Original Message -----
From: "Stian Thorgersen" <sthorger(a)redhat.com>
To: "Pedro Igor Silva" <psilva(a)redhat.com>
Cc: "keycloak dev" <keycloak-dev(a)lists.jboss.org>
Sent: Friday, October 16, 2015 5:15:56 AM
Subject: Re: [keycloak-dev] Authz Model Implementation
For now - which ever you want. I propose you introduce a new SPI though.
Once it's beyond a POC then both :/
On 14 October 2015 at 15:40, Pedro Igor Silva <psilva(a)redhat.com> wrote:
Hi,
Would like to know your thoughts about which model implementations I
must support for the authz model. Both Database/JPA and MongoDB ?
Regards.
Pedro Igor
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev