I would not recommend trying to completely replace the DB layer with NoSQL.
That would mean you'd need to store realms, clients, roles, etc.. This also
regularly change from release to release so you would have to update your
implementation regularly.
For users only the user storage SPI is a supported API and we will maintain
backwards compatibility there. Although, personally I would rather just use
the same relational db for both rather than having to maintain both a
relational db and a NoSQL db.
On 29 May 2018 at 07:50, Pulkit Srivastava <pulkitsrivastavajd(a)gmail.com>
wrote:
Hey,
Any pointer to this?
Thanks,
Pulkit
On Mon, May 28, 2018 at 1:06 PM, Pulkit Srivastava <
pulkitsrivastavajd(a)gmail.com> wrote:
> Thanks for the prompt reply.
>
> I found the following blog regarding removing support for MongoDB which
is
> a NoSQL db :
https://blog.keycloak.org/2017/02/removing-mongo-
> support-from-keycloak.html
>
> I am worried since i am also going to integrate a NoSQL db(amazon dynamo
> db) with keycloak. Is there a possibility that I might also face the same
> problems the blog talks about with little or no support from Keycloak
> support team.
>
> Also, do we have anyone from the keycloak users, who have tried
> integrating amazon dynamo db with Keycloak and has been successful in
doing
> so.
>
> Thanks,
> Pulkit
>
>
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user