Thanks for looking into databases. Right now, Keycloak should work on MySQL, PostgreSQL, Oracle and Sybase. Still looking on MS-SQL and IBM DB2 and I've created separate issue KEYCLOAK-303 for it, as it seems that MS-SQL issue is not related to ID generation. I will reply once I have luck with MS-SQL, so you can test in your environment.
Thanks,
Marek
On 18.2.2014 21:59, Bill Burke wrote:
RealmEntity's ID is set manually and uses the same code as JpaIdGenerator. I think Marek is looking into MSSQL. On 2/18/2014 3:49 PM, Dean Peterson wrote:Hello, I realize you are still in development for the alpha2 release. Thank you for making the change to UUID rather than Identity String columns. I noticed I can now deploy to a Postgresql database but I still fail on MSSQL because the RealmEntity class has not been converted to use the new identity mechanism. I am sure this would have been updated before alpha2 was released but I wanted to bring some attention to it just in case. Thanks, Dean _______________________________________________ keycloak-user mailing list keycloak-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-user
_______________________________________________ keycloak-user mailing list keycloak-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-user