From your knowledge has anyone achieved that ??

Hi, You do not need to deploy the server to Tomcat to be able to use Keycloak in your apps deployed to Tomcat. We only support deploying Keycloak server to latest version of WildFly and JBoss EAP. Further we highly recommend using the standalone download of Keycloak and running it separately to your applications. On 26 November 2015 at 07:24, mohammed althaf <althaf1088(a)gmail.com&gt; wrote: > Hi Team, > > I was able to use keycloak for sso seamlessly in jboss /wildfly server. > > Since my web application is running in tomcat ,i am trying to deploy the > keycloak server as well in Tomcat, > > I followed > > https://reachmnadeem.wordpress.com/2015/01/14/deploying-keycloak-in-tomcat/ > > and i was able to spin up the keycloak in tomcat server.But it was using > the 1.0.2 version. > > So i am trying to deploy the keycloak server 1.6.1.I faced the below > issues. > > 1.Failed to provide mem for realmcache(please check failed to find > provider log) > > So i removed the cache from keycloak-server.json > Not sure it is fine?? > > 2 .Then i was able to procced but it again failed with h2.db > exception(please check lockout.log) > > It will be great if you guys can help me resolve this issue. > > Thanks, > Althaf > > > > > _______________________________________________ > keycloak-dev mailing list > keycloak-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/keycloak-dev >

In enterprise they should recommend using a standalone SSO server. It's more secure and scalable. You wouldn't embed your database into Tomcat would you? It's also more reliable and less error prone as you are using the exact bits that we test. It has been achieved in the past, but initially we relied less on features from WildFly. Keycloak server is no longer a WAR that's deployed onto the WildFly app server, instead we rely on the core bits of WildFly to create our own dedicated server. In theory it would be possible to get it to work on top of Tomcat with some considerable amount of effort. However, as we add new features in the future that rely on features in WildFly you would have new issues. Further we would not be able to help you if you have any issues.

On 26 November 2015 at 08:54, mohammed althaf <althaf1088(a)gmail.com <mailto:althaf1088@gmail.com>> wrote: Hi Stian, Thanks for your quick reply.Yeah i have tried the Tomcat adapters for keycloak Integration. I just want to explore the option to deploy it in tomcat itself ,since in enterprise if they already use tomcat for applications they wont recommend to use another server for SSO alone. From your knowledge has anyone achieved that ?? Thanks, Althaf On 26 November 2015 at 15:40, Stian Thorgersen <sthorger(a)redhat.com <mailto:sthorger@redhat.com>> wrote: Hi, You do not need to deploy the server to Tomcat to be able to use Keycloak in your apps deployed to Tomcat. We only support deploying Keycloak server to latest version of WildFly and JBoss EAP. Further we highly recommend using the standalone download of Keycloak and running it separately to your applications. On 26 November 2015 at 07:24, mohammed althaf <althaf1088(a)gmail.com <mailto:althaf1088@gmail.com>> wrote: Hi Team, I was able to use keycloak for sso seamlessly in jboss /wildfly server. Since my web application is running in tomcat ,i am trying to deploy the keycloak server as well in Tomcat, I followed https://reachmnadeem.wordpress.com/2015/01/14/deploying-keycloak-in-tomcat/ and i was able to spin up the keycloak in tomcat server.But it was using the 1.0.2 version. So i am trying to deploy the keycloak server 1.6.1.I faced the below issues. 1.Failed to provide mem for realmcache(please check failed to find provider log) So i removed the cache from keycloak-server.json Not sure it is fine?? 2 .Then i was able to procced but it again failed with h2.db exception(please check lockout.log) It will be great if you guys can help me resolve this issue. Thanks, Althaf _______________________________________________ keycloak-dev mailing list keycloak-dev(a)lists.jboss.org <mailto:keycloak-dev@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/keycloak-dev _______________________________________________ keycloak-dev mailing list keycloak-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-dev

Infinispan (caching), JPA, datasources, servlet, JAX-RS. Wildfly/JBoss is also set to run out of the box in a cluster and managable in a domain ( a cluster) out of the box. Not to mention all the classloader isolation you DO NOT get with Tomcat. Finally all the built in patch management that comes with Wildfly/JBoss. Then there's developers that will want to deploy integration/extension plugins. We can also leverage Wildfly's deployment engine for that too. Running Keycloak Auth Server in Tomcat/Jetty would actually not be a very smart thing to do. There are huge advantages to running within Wildfly/JBoss. The only disadvantage is the size of the distro. There is no performance penalty.

We have looked into trimming the Wildfly distro, but nixed that because it puts a huge burden on productization. Its just much easier for them if we just layer on top of the full app server.