KEYCLOAK-11239 Fix links reported by SecuringAppsTest
This commit is contained in:
parent
327e60c5e0
commit
600d5ca66c
4 changed files with 8 additions and 8 deletions
|
@ -15,9 +15,9 @@ Security for the following items is supported for Fuse:
|
|||
|
||||
* Classic WAR applications deployed on Fuse with Pax Web War Extender
|
||||
* Servlets deployed on Fuse as OSGI services with 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
|
||||
* https://camel.apache.org/[Apache Camel] Jetty endpoints running with the https://camel.apache.org/components/latest/jetty-component.html[Camel Jetty] component
|
||||
* https://cxf.apache.org/[Apache CXF] endpoints running on their own separate https://cxf.apache.org/docs/jetty-configuration.html[Jetty engine]
|
||||
* https://cxf.apache.org/[Apache CXF] endpoints running on the default engine provided by the CXF servlet
|
||||
* SSH and JMX admin access
|
||||
* https://hawt.io/[Hawtio administration console]
|
||||
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
===== Securing an Apache Camel Application
|
||||
|
||||
You can secure Apache Camel endpoints implemented with the http://camel.apache.org/jetty.html[camel-jetty] component by adding securityHandler with `KeycloakJettyAuthenticator` and the proper security constraints injected. You can add the `OSGI-INF/blueprint/blueprint.xml` file to your Camel application with a similar configuration as below. The roles, security constraint mappings, and {project_name} adapter configuration might differ slightly depending on your environment and needs.
|
||||
You can secure Apache Camel endpoints implemented with the https://camel.apache.org/components/latest/jetty-component.html[camel-jetty] component by adding the securityHandler with `KeycloakJettyAuthenticator` and the proper security constraints injected. You can add the `OSGI-INF/blueprint/blueprint.xml` file to your Camel application with a similar configuration as below. The roles, security constraint mappings, and {project_name} adapter configuration might differ slightly depending on your environment and needs.
|
||||
|
||||
For example:
|
||||
|
||||
|
|
|
@ -20,9 +20,9 @@ Security for the following items is supported for Fuse:
|
|||
* Classic WAR applications deployed on Fuse with Pax Web War Extender
|
||||
* Servlets deployed on Fuse as OSGI services with Pax Web Whiteboard Extender and additionally servlets registered through
|
||||
org.osgi.service.http.HttpService#registerServlet() which is standard OSGi Enterprise HTTP Service
|
||||
* http://camel.apache.org/[Apache Camel] Undertow endpoints running with the http://camel.apache.org/undertow.html[Camel Undertow] component
|
||||
* http://cxf.apache.org/[Apache CXF] endpoints running on their own separate Undertow engine
|
||||
* http://cxf.apache.org/[Apache CXF] endpoints running on the default engine provided by the CXF servlet
|
||||
* https://camel.apache.org/[Apache Camel] Undertow endpoints running with the https://camel.apache.org/components/latest/undertow-component.html[Camel Undertow] component
|
||||
* https://cxf.apache.org/[Apache CXF] endpoints running on their own separate Undertow engine
|
||||
* https://cxf.apache.org/[Apache CXF] endpoints running on the default engine provided by the CXF servlet
|
||||
* SSH and JMX admin access
|
||||
* https://hawt.io/[Hawtio administration console]
|
||||
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
[[_fuse7_adapter_camel]]
|
||||
===== Securing an Apache Camel Application
|
||||
|
||||
You can secure Apache Camel endpoints implemented with the http://camel.apache.org/undertow.html[camel-undertow] component by injecting the proper security constraints via blueprint and updating the used component to `undertow-keycloak`. You have to add the `OSGI-INF/blueprint/blueprint.xml` file to your Camel application with a similar configuration as below. The roles and security constraint mappings, and adapter configuration might differ slightly depending on your environment and needs.
|
||||
You can secure Apache Camel endpoints implemented with the https://camel.apache.org/components/latest/undertow-component.html[camel-undertow] component by injecting the proper security constraints via blueprint and updating the used component to `undertow-keycloak`. You have to add the `OSGI-INF/blueprint/blueprint.xml` file to your Camel application with a similar configuration as below. The roles, security constraint mappings, and adapter configuration might differ slightly depending on your environment and needs.
|
||||
|
||||
Compared to the standard `undertow` component, `undertow-keycloak` component adds two new properties:
|
||||
|
||||
|
|
Loading…
Reference in a new issue