keycloak-scim/examples/fuse

Keycloak Fuse demo

Currently Keycloak supports securing your web applications running inside JBoss Fuse or Apache Karaf. It leverages Jetty8 adapter as both JBoss Fuse 6.1 and Apache Karaf 3 are bundled with Jetty8 server under the covers and Jetty is used for running various kinds of web applications.

The Fuse example is slightly modified version of Keycloak base demo applications. The main difference among base demo is that for Fuse demo are applications running on separate Fuse/Karaf server. Keycloak server is supposed to run separately on Wildfly 8 or JBoss EAP 6.3.

What is supported for Fuse/Karaf is:

• Security for classic WAR applications deployed on Fuse/Karaf with pax-war extender.
• Security for servlets deployed on Fuse/Karaf as OSGI services with pax-whiteboard extender.
• Security for Apache Camel Jetty endpoints running with camel-jetty component.
• Security for Apache CXF endpoints running on their own separate Jetty engine. Supports both securing JAX-RS and JAX-WS endpoints.
• Security for Apache CXF endpoints running on default engine provided by CXF servlet on http://localhost:8181/cxf

Fuse demo contains those basic applications:

• customer-app-fuse A WAR application that is deployed with pax-war extender
• product-app-fuse A servlet application deployed with pax-whiteboard extender
• cxf-jaxws Apache CXF JAX-WS endpoint running on separate Jetty engine on http://localhost:8282/PersonServiceCF. The product-app-fuse invokes the endpoint to get data.
• camel Apache Camel endpoint running on separate Jetty engine on http://localhost:8383/admin-camel-endpoint. The customer-app-fuse invokes the endpoint to get data.
• cxf-jaxrs Apache CXF JAX-RS endpoint running on default Jetty on http://localhost:8181/cxf/customerservice. The customer-app-fuse invokes the endpoint to get data

Running of demo consists of 2 steps. First you need to run separate Keycloak server and then Fuse/Karaf server with the applications

Base steps

• Run external instance of Keycloak server on WildFly 8 or JBoss EAP 6.3 . Fuse demo suppose that server is running on http://localhost:8080/auth
• Import realm demo from the file testrealm.json on examples/fuse/testrealm.json . See here the details on how to import the realm
• Then build examples, which is needed so the feature repository is added to your local maven repo:

cd examples/fuse
mvn clean install

Run demo applications on Apache Karaf 3.0.2

Demo is using Apache camel and Apache CXF, which are not in standalone Karaf by default. So you will need to install feature repositories for both of them. Next step is to add feature repository for main set of Keycloak karaf features and for the demo. Once all feature URLs are added, you just need to install keycloak-fuse-example feature, which automatically installs all other needed stuff.

Once you run Apache Karaf, you need to run these commands from Karaf console (Make sure to replace keycloak versions in the example with actual Keycloak version):

feature:repo-add mvn:org.apache.camel.karaf/apache-camel/2.12.5/xml/features
feature:repo-add mvn:org.apache.cxf.karaf/apache-cxf/2.7.14/xml/features
feature:repo-add mvn:org.keycloak/keycloak-osgi-features/1.2.0.Beta1/xml/features
feature:repo-add mvn:org.keycloak.example.demo/keycloak-fuse-example-features/1.2.0.Beta1/xml/features
feature:install keycloak-fuse-example

After that you can test running on http://localhost:8181/customer-portal and login as "bburke@redhat.com" with password "password". Customer-portal is able to receive the response from the endpoints provided by cxf-jaxrs and camel applications. Note that camel endpoint is available just for users with role admin in this demo, so "bburke@redhat.com" can't access it. You may login as "admin" with password "password" in order to invoke camel endpoint.

From http://localhost:8181/product-portal you will see servlet endpoint, which invokes JAX-WS provided by cxf-jaxws application.

Note that this demo also secures whole default CXF endpoint on http://localhost:8181/cxf hence every application running under it is secured too.

Running example on JBoss Fuse 6.1.0.redhat-379

Securing your applications on JBoss Fuse 6.1 is a bit more tricky. There is bug https://ops4j1.jira.com/browse/PAXWEB-666 , which doesn't easily allow to secure default Jetty engine on http://localhost:8181 as it's not possible to inject custom Jetty authenticator provided by Keycloak Jetty adapter into underlying Jetty server. Hence first step is to upgrade pax-web version from default 3.0.6 to newer 3.1.2 . Then you need to "refresh" cxf feature too. Final step is to install "keycloak-fuse-example" feature.

All the steps could be performed with these commands in Fuse console (Replace Keycloak versions with the current Keycloak version number):

features:uninstall pax-war
features:uninstall pax-http-whiteboard 
features:uninstall pax-http
features:uninstall pax-jetty
features:removeurl mvn:org.ops4j.pax.web/pax-web-features/3.0.6/xml/features

Now restart fuse (use osgi:shutdown command and start it again from command line. You can ignore startup messages after restart as pax-web is not installed at the moment. Then run those commands:

features:addurl mvn:org.ops4j.pax.web/pax-web-features/3.1.2/xml/features
features:addurl mvn:org.keycloak/keycloak-osgi-features/1.2.0.Beta1/xml/features
features:addurl mvn:org.keycloak.example.demo/keycloak-fuse-example-features/1.2.0.Beta1/xml/features
features:install keycloak-pax-web-upgrade
features:install pax-http-whiteboard/3.1.2
features:install pax-war/3.1.2

Now it's recommended to restart again. After the start, you shouldn't see any error messages, which indicates that upgrade to pax-web 3.1.2 went fine. So last step is to install the demo now:

features:install keycloak-fuse-example

Now you can test example applications similarly like described for "Karaf" section.

Running example on JBoss Fuse 6.2.0

This is snapshot version of JBoss Fuse, which is not released yet at this moment. It has pax-web bug mentioned above fix already, so just those commands are sufficient to install the demo (Replace Keycloak versions with the current Keycloak version number):

features:addurl mvn:org.keycloak/keycloak-osgi-features/1.2.0.Beta1/xml/features
features:addurl mvn:org.keycloak.example.demo/keycloak-fuse-example-features/1.2.0.Beta1/xml/features
features:install keycloak-fuse-example

Now you can test example applications similarly like described for "Karaf" section.

How to secure your own applications

Most of the steps should be understandable from testing and understanding the demo. Basically all mentioned applications require to inject Keycloak Jetty authenticator into underlying Jetty server . The steps are bit different according to application type.

Classic WAR application - Take a look at customer-portal-app for inspiration. The needed steps are:

• Declare needed constraints in /WEB-INF/web.xml
• Add jetty-web.xml file with the authenticator to /WEB-INF/jetty-web.xml and add /WEB-INF/keycloak.json with your Keycloak configuration
• Make sure your WAR imports org.keycloak.adapters.jetty and maybe some more packages in MANIFEST.MF file in header Import-Package. It's recommended to use maven-bundle-plugin similarly like Fuse examples are doing, but note that "*" resolution for package doesn't import org.keycloak.adapters.jetty package as it's not used by application or Blueprint or Spring descriptor, but it's used just in jetty-web.xml file.

Servlet web application deployed by pax-whiteboard-extender - Take a look at product-portal-app for inspiration. The needed steps are:

• Keycloak provides PaxWebIntegrationService, which allows to inject jetty-web.xml and configure security constraints for your application. Example product-portal-app declares this in OSGI-INF/blueprint/blueprint.xml . Note that your servlet needs to depend on it.
• Steps 2,3 are same like for classic WAR

Apache camel application - You can secure your Apache camel endpoint using camel-jetty endpoint by adding securityHandler with KeycloakJettyAuthenticator and proper security constraints injected. Take a look at OSGI-INF/blueprint/blueprint.xml configuration in camel application on example of how it can be done.

Apache CXF endpoint - It's recommended to run your CXF endpoints secured by Keycloak on separate Jetty engine. Application cxf-ws is using separate endpoint on http://localhost:8282 . All the important configuration is declared in cxf-jaxws app in META-INF/spring/beans.xml .

Builtin web applications - Some services automatically come with deployed servlets on startup. One of such examples is CXF servlet running on http://localhost:8181/cxf context. Securing such endpoints is quite tricky. The approach, which Keycloak is currently using, is providing ServletReregistrationService, which undeploys builtin servlet at startup, so you are able to re-deploy it again on context secured by Keycloak. You can see the OSGI-INF/blueprint/blueprint.xml inside cxf-jaxrs project, which adds JAX-RS "customerservice" endpoint and more importantly, it secures whole /cxf context.

As a side effect, all other CXF services running on default CXF HTTP destination will be secured too. Once you uninstall feature "keycloak-fuse-example" the original unsecured servlet on /cxf context is deployed back and hence context will become unsecured again.

It's recommended to use your own Jetty engine for your apps (similarly like cxf-jaxws application is doing).

How to secure Fuse admin services

It's possible to secure fuse admin services with Keycloak too. See fuse-admin for info on how to secure Fuse admin console, remote SSH and JMX access with Keycloak.