I propose that we move the adapters for PicketLink and MongoDB into separate Maven modules. IMO the code in services is already a bit crowded, and with the addition of a MongoDB implementation it will only get worse. If we add a SPI for these it would be easier in the future to add more. It would also be possible for users to write their own if they really need to. This will also make it possible for us to release M1 with either PicketLink or MongoDB even if the non-default implementation is not fully working at the time. _______________________________________________ keycloak-dev mailing list keycloak-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-dev

I wonder why PicketLink IDM is viewed at par with MongoDB here. Would it not be better if MongoDB Identity Store implementation was added to PicketLink and that was used? That way KeyCloak API could depend on PicketLink IDM API for file, ldap,DB,mongodb,cassandra,HDFS,HBase (and you name it) identity stores. I know we do not yet have implementations for identity stores for mongo,cassandra etc in PL yet. On 09/20/2013 06:45 AM, Stian Thorgersen wrote: > I propose that we move the adapters for PicketLink and MongoDB into separate Maven modules. IMO the code in services is already a bit crowded, and with the addition of a MongoDB implementation it will only get worse. If we add a SPI for these it would be easier in the future to add more. It would also be possible for users to write their own if they really need to. > > This will also make it possible for us to release M1 with either PicketLink or MongoDB even if the non-default implementation is not fully working at the time. _______________________________________________ keycloak-dev mailing list keycloak-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-dev