Java Reference
In-Depth Information
Within the web subsystem, you have to first change the default
schema
and
socket-binding
to
"https"
and add the
secure
element to it. Next, you have
to insert an
ssl
stanza within it, which contains the details of your
keystore
object
(in our example, we have dropped the file
jboss.keystore
into the server config-
uration directory):
<subsystem xmlns="urn:jboss:domain:web:1.1"
default-virtual-server="default-host"
native="false">
<connector name="http" protocol="HTTP/1.1"
scheme="https" socket-binding="https"
secure="true">
<ssl key-alias="as7alias"
password="mypassword"
certificate-key-file="${jboss.server.config.dir}/
jboss.keystore"
cipher-suite="ALL" protocol="TLS"/>
</connector>
. . . . . .
</subsystem>
You have to restart the JBoss AS to activate the changes. You should see the fol-
lowing log at the bottom of your console, which informs you about the new HTTPS
channel running on port 8443.
INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4)
Starting Coyote HTTP/1.1 on http--127.0.0.1-8443:
The following screen is what will be displayed by the Internet Explorer browser
(the same kind of error message, with a different format, will be displayed by other
browsers such as Firefox and Google Chrome) if you try to access the Ticket
example using the secured channel (for example,
https://localhost:8443/
ticket-agency-cdi
):
