[keycloak-dev] Storage SPI: Users, Clients, and ?

Pedro Igor Silva psilva at redhat.com
Mon Jun 10 08:03:10 EDT 2019


Hi Justin,

Personally, I think that having a single and multi-purpose SPI can lead to
a much more complex and full of hacks to address the different requirements
when integrating with different sources and data. In any case, I would
suggest you to start a design document and send a PR to
https://github.com/keycloak/keycloak-community. So we can understand better
your proposal and discuss it.

Regards.
Pedro Igor

On Sun, Jun 9, 2019 at 12:10 AM Justin Gross <jgross.biz at gmail.com> wrote:

> Born out of necessity it looks like originally (for storage SPI) there was
> only user storage SPI and eventually came a partial client storage SPI
> motivated by a need for Openshift integration. The more I think about how
> it could be finished, and the more I look at the user storage SPI, the more
> I am finding code within user storage SPI that can be generalized as simply
> storage SPI.
>
> Seeking feedback on refactoring existing user storage SPI related
> interfaces to be agnostic to users and generalized as “storage SPI”. This
> should reduce the need for duplicating similar code when implementing other
> storage SPI (ie: client storage SPI).
>
> In the future I could see more storage SPI’s being created and I feel this
> would be extremely useful.
>
>
> Thank you,
>
> Justin Gross
> _______________________________________________
> keycloak-dev mailing list
> keycloak-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/keycloak-dev


More information about the keycloak-dev mailing list