keycloak-scim/securing_apps/topics/oidc/java/fuse-adapter.adoc

32 lines
2.2 KiB
Text
Raw Normal View History

2016-04-18 19:10:32 +00:00
[[_fuse_adapter]]
2016-06-09 13:12:10 +00:00
==== JBoss Fuse Adapter
2016-04-18 19:10:32 +00:00
2016-12-02 19:54:19 +00:00
Currently {{book.project.name}} supports securing your web applications running inside http://developers.redhat.com/products/fuse/overview/[JBoss Fuse].
2016-06-10 05:37:09 +00:00
{% if book.community %}
It leverages <<fake/../jetty9-adapter.adoc#_jetty9_adapter,Jetty 9 adapter>> as {{book.fuseVersion}} is bundled with http://eclipse.org/jetty/[Jetty 9.2 server]
2016-06-02 14:29:37 +00:00
under the covers and Jetty is used for running various kinds of web applications.
2016-06-10 05:37:09 +00:00
{% endif %}
2016-04-18 19:10:32 +00:00
WARNING: The only supported version of Fuse is {{book.fuseVersion}}. If you use earlier versions of Fuse, it is possible that some functions will not work correctly. In particular, the http://hawt.io[Hawtio] integration will not work with earlier versions of Fuse.
Security for the following items is supported for Fuse:
2016-04-18 19:10:32 +00:00
* Classic WAR applications deployed on Fuse with https://ops4j1.jira.com/wiki/display/ops4j/Pax+Web+Extender+-+War[Pax Web War Extender]
* Servlets deployed on Fuse as OSGI services with https://ops4j1.jira.com/wiki/display/ops4j/Pax+Web+Extender+-+Whiteboard[Pax Web Whiteboard Extender]
* http://camel.apache.org/[Apache Camel] Jetty endpoints running with the http://camel.apache.org/jetty.html[Camel Jetty] component
* http://cxf.apache.org/[Apache CXF] endpoints running on their own separate http://cxf.apache.org/docs/jetty-configuration.html[Jetty engine]
* http://cxf.apache.org/[Apache CXF] endpoints running on the default engine provided by the CXF servlet
* SSH and JMX admin access
* http://hawt.io[Hawtio administration console]
2016-04-18 19:10:32 +00:00
===== Securing Your Web Applications Inside Fuse
2016-06-02 14:29:37 +00:00
You must first install the {{book.project.name}} Karaf feature. Next you will need to perform the steps according to the type of application you want to secure.
All referenced web applications require injecting the {{book.project.name}} Jetty authenticator into the underlying Jetty server. The steps to achieve this depend on the application type. The details are described below.
2016-06-02 14:29:37 +00:00
{% if book.community %}
The best place to start is look at Fuse demo bundled as part of {{book.project.name}} examples in directory `fuse` . Most of the steps should be understandable from testing and
understanding the demo.
{% endif %}