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

33 lines
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-06-13 11:02:36 +00:00
{% if book.product %}
2016-06-01 11:30:02 +00:00
NOTE: JBoss Fuse is a Technology Preview feature and is not fully supported
2016-06-13 11:02:36 +00:00
{% endif %}
2016-06-01 11:30:02 +00:00
Currently {{book.project.name}} supports securing your web applications running inside http://www.jboss.org/products/fuse/overview/[JBoss Fuse] .
2016-06-10 05:37:09 +00:00
{% if book.community %}
It leverages <<fake/../jetty8-adapter.adoc#_jetty8_adapter,Jetty 8 adapter>> as both JBoss Fuse 6.2 are bundled with http://eclipse.org/jetty/[Jetty 8.1 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
What is supported for Fuse is:
2016-04-18 19:10:32 +00:00
* Security for classic WAR applications deployed on Fuse with https://ops4j1.jira.com/wiki/display/ops4j/Pax+Web+Extender+-+War[Pax Web War Extender].
* Security for servlets deployed on Fuse as OSGI services with https://ops4j1.jira.com/wiki/display/ops4j/Pax+Web+Extender+-+Whiteboard[Pax Web Whiteboard Extender].
2016-04-18 19:10:32 +00:00
* Security for http://camel.apache.org/[Apache Camel] Jetty endpoints running with http://camel.apache.org/jetty.html[Camel Jetty] component.
* Security for http://cxf.apache.org/[Apache CXF] endpoints running on their own separate http://cxf.apache.org/docs/jetty-configuration.html[Jetty engine].
* Security for http://cxf.apache.org/[Apache CXF] endpoints running on default engine provided by CXF servlet.
2016-06-02 14:29:37 +00:00
* Security for SSH and JMX admin access.
2016-04-18 19:10:32 +00:00
2016-06-09 13:12:10 +00:00
===== How to secure your web applications inside Fuse
2016-06-02 14:29:37 +00:00
2016-09-06 09:45:57 +00:00
The first thing to do is usually installing of {{book.project.name}} Karaf feature. Then do the steps according to what type of application you want to secure.
Basically all mentioned web applications require to inject {{book.project.name}} Jetty authenticator into underlying Jetty server . The steps to achieve it are bit different
according to application type. The details are described in individual sub-chapters.
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 %}