Update namespace for urn:jboss:domain:undertow in product guides
This commit is contained in:
parent
08ca85f19e
commit
cf18563e95
11 changed files with 49 additions and 20 deletions
|
@ -45,6 +45,10 @@
|
|||
"keycloakinstallclientadapter": {
|
||||
"name": "Installing the Client Adapter",
|
||||
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-beta/html-single/getting-started-guide/#installing_the_client_adapter"
|
||||
},
|
||||
|
||||
"subsystem": {
|
||||
"undertow": "urn:jboss:domain:undertow:3.1"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
|
@ -95,6 +95,10 @@
|
|||
"name": "WildFly 10 Documentation",
|
||||
"link": "https://docs.jboss.org/author/display/WFLY10/JPA+Reference+Guide#JPAReferenceGuide-Hibernateproperties"
|
||||
}
|
||||
},
|
||||
|
||||
"subsystem": {
|
||||
"undertow": "urn:jboss:domain:undertow:3.0"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
0
build-product.sh
Normal file → Executable file
0
build-product.sh
Normal file → Executable file
|
@ -38,6 +38,10 @@
|
|||
"name": "Quickstarts for the Red Hat Single Sign-On (SSO) Server",
|
||||
"dir": "redhat-sso-quickstarts",
|
||||
"link": "https://github.com/redhat-developer/redhat-sso-quickstarts"
|
||||
},
|
||||
|
||||
"subsystem": {
|
||||
"undertow": "urn:jboss:domain:undertow:3.1"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
|
@ -25,6 +25,10 @@
|
|||
"name": "Server Administration Guide",
|
||||
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-beta/html-single/server-administration-guide/"
|
||||
},
|
||||
"fuseVersion": "JBoss Fuse 6.3.0 Rollup 1"
|
||||
"fuseVersion": "JBoss Fuse 6.3.0 Rollup 1",
|
||||
|
||||
"subsystem": {
|
||||
"undertow": "urn:jboss:domain:undertow:3.1"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
|
@ -32,6 +32,10 @@
|
|||
"adapterguide": {
|
||||
"name": "Securing Applications and Services Guide",
|
||||
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-beta/html-single/securing-applications-and-services-guide/"
|
||||
},
|
||||
|
||||
"subsystem": {
|
||||
"undertow": "urn:jboss:domain:undertow:3.1"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
|
@ -111,8 +111,9 @@ See link:https://docs.jboss.org/author/display/WFLY10/Admin+Guide#AdminGuide-HTT
|
|||
|
||||
* Add the <https-listener> element as shown below:
|
||||
|
||||
```
|
||||
<subsystem xmlns="urn:jboss:domain:undertow:3.0">
|
||||
[source,xml,subs="attributes+"]
|
||||
----
|
||||
<subsystem xmlns="{{book.subsystem.undertow}}">
|
||||
....
|
||||
<server name="default-server">
|
||||
<https-listener name="default"
|
||||
|
@ -121,7 +122,7 @@ See link:https://docs.jboss.org/author/display/WFLY10/Admin+Guide#AdminGuide-HTT
|
|||
verify-client="REQUESTED"/>
|
||||
</server>
|
||||
</subsystem>
|
||||
```
|
||||
----
|
||||
|
||||
`https-listener/security-realm`::
|
||||
The value must match the name of the realm from the previous section
|
||||
|
|
|
@ -39,6 +39,10 @@
|
|||
"adapterguide": {
|
||||
"name": "JavaScript OpenID Connect Adapter",
|
||||
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-beta/html-single/securing-applications-and-services-guide#javascript_adapter"
|
||||
},
|
||||
|
||||
"subsystem": {
|
||||
"undertow": "urn:jboss:domain:undertow:3.1"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
|
@ -62,6 +62,10 @@
|
|||
"adminguide": {
|
||||
"name": "Server Administration Guide",
|
||||
"link": "https://access.redhat.com/documentation/en/red-hat-single-sign-on/7.1-Beta/html-single/server-administration-guide/"
|
||||
},
|
||||
|
||||
"subsystem": {
|
||||
"undertow": "urn:jboss:domain:undertow:3.1"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
|
@ -35,12 +35,12 @@ Beyond the proxy itself, there are a few things you need to configure on the {{b
|
|||
If your proxy is forwarding requests via the HTTP protocol, then you need to configure {{book.project.name}} to pull the client's
|
||||
IP address from the `X-Forwarded-For` header rather than from the network packet.
|
||||
To do this, open up the profile configuration file (_standalone.xml_, _standalone-ha.xml_, or _domain.xml_ depending on your
|
||||
<<fake/../../operating-mode.adoc#_operating-mode, operating mode>>) and look for the `"urn:jboss:domain:undertow:3.0` XML block.
|
||||
<<fake/../../operating-mode.adoc#_operating-mode, operating mode>>) and look for the `{{book.subsystem.undertow}}` XML block.
|
||||
|
||||
.`X-Forwarded-For` HTTP Config
|
||||
[source,xml]
|
||||
[source,xml,subs="attributes+"]
|
||||
----
|
||||
<subsystem xmlns="urn:jboss:domain:undertow:3.0">
|
||||
<subsystem xmlns="{{book.subsystem.undertow}}">
|
||||
<buffer-cache name="default"/>
|
||||
<server name="default-server">
|
||||
<ajp-listener name="ajp" socket-binding="ajp"/>
|
||||
|
@ -60,9 +60,9 @@ pull this information from the AJP packets.
|
|||
|
||||
|
||||
.`X-Forwarded-For` AJP Config
|
||||
[source,xml]
|
||||
[source,xml,subs="attributes+"]
|
||||
----
|
||||
<subsystem xmlns="urn:jboss:domain:undertow:3.0">
|
||||
<subsystem xmlns="{{book.subsystem.undertow}}">
|
||||
<buffer-cache name="default"/>
|
||||
<server name="default-server">
|
||||
<ajp-listener name="ajp" socket-binding="ajp"/>
|
||||
|
@ -85,9 +85,9 @@ pull this information from the AJP packets.
|
|||
==== Enable HTTPS/SSL with a Reverse Proxy
|
||||
|
||||
Assuming that your reverse proxy doesn't use port 8443 for SSL you also need to configure what port HTTPS traffic is redirected to.
|
||||
[source,xml]
|
||||
[source,xml,subs="attributes+"]
|
||||
----
|
||||
<subsystem xmlns="urn:jboss:domain:undertow:3.0">
|
||||
<subsystem xmlns="{{book.subsystem.undertow}}">
|
||||
...
|
||||
<http-listener name="default" socket-binding="http"
|
||||
proxy-address-forwarding="true" redirect-socket="proxy-https"/>
|
||||
|
@ -153,9 +153,9 @@ file and go to the undertow configuration in the `load-balancer` profile. Add a
|
|||
`remote-host3` within the `reverse-proxy` XML block.
|
||||
|
||||
.domain.xml reverse-proxy config
|
||||
[source,xml]
|
||||
[source,xml,subs="attributes+"]
|
||||
----
|
||||
<subsystem xmlns="urn:jboss:domain:undertow:3.0">
|
||||
<subsystem xmlns="{{book.subsystem.undertow}}">
|
||||
...
|
||||
<handlers>
|
||||
<reverse-proxy name="lb-handler">
|
||||
|
|
|
@ -124,7 +124,7 @@ the keystore and enable HTTPS. (See <<fake/../../operating-mode.adoc#_operating
|
|||
|
||||
In the standalone or domain configuration file, search for the `security-realms` element and add:
|
||||
|
||||
[source]
|
||||
[source,xml]
|
||||
----
|
||||
|
||||
<security-realm name="UndertowRealm">
|
||||
|
@ -136,11 +136,11 @@ In the standalone or domain configuration file, search for the `security-realms`
|
|||
</security-realm>
|
||||
----
|
||||
|
||||
Find the element `server name="default-server"` (it's a child element of `subsystem xmlns="urn:jboss:domain:undertow:`) and add:
|
||||
Find the element `server name="default-server"` (it's a child element of `subsystem xmlns="{{book.subsystem.undertow}}"`) and add:
|
||||
|
||||
[source]
|
||||
[source,xml,subs="attributes+"]
|
||||
----
|
||||
<subsystem xmlns="urn:jboss:domain:undertow:3.0">
|
||||
<subsystem xmlns="{{book.subsystem.undertow}}">
|
||||
<buffer-cache name="default"/>
|
||||
<server name="default-server">
|
||||
<https-listener name="https" socket-binding="https" security-realm="UndertowRealm"/>
|
||||
|
|
Loading…
Reference in a new issue