Java Reference
In-Depth Information
adminUser=admin123
The following is the corresponding
ejb-roles.properties
file that grants the role
ejbRole
to the
adminUser
role:
adminUser=ejbRole
The last configuration effort would be to specify it in the
security-realm
attribute of
your
remoting
connector's element:
<subsystem xmlns="urn:jboss:domain:remoting:2.0">
<endpoint worker="default"/>
<http-connector name="http-remoting-connector"
connector-ref="default"
security-realm="EJBRealm"/>
</subsystem>
Let's check the outcome of our work. First, we will try out the HTTPS connection.
You have to restart WildFly to activate the changes. You should see the following log at
the bottom of your console, which informs you about the new HTTPS channel running on
port 8443:
[org.wildfly.extension.undertow] (MSC service thread 1-9)
JBAS017519: Undertow HTTP listener default listening on
/127.0.0.1:8443
The following screen is what will be displayed by the Internet Explorer (don't try this at
home) 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 ex-
ample using the secured channel (for example,
https://localhost:8443/
ticket-agency-cdi
):
