Securing JBoss AS 7 Applications - JBoss AS 7 Development - page 362

security-realm="EJBRealm"/>
</subsystem>
Creating an SSL-aware security realm
As we have learned in Chapter 3 , Beginning Java EE 6 - EJBs , the RMI-IIOP
connection properties are specified in the jboss-ejb-client.properties file,
which needs to be tweaked a bit to enable SSL connections:
remote.connections=node1
remote.connection.node1.host=localhost
remote.connection.node1.port = 4447
remote.connection.node1.username=adminUser
remote.connection.node1.password=admin123
remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=true
remote.connection.node1.connect.options.org.xnio.Options.SSL_STARTTLS=true
remote.connection.node1.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=true
The SSL_ENABLED option, when set to true , enables the remoting connector's
SSL communication.
The STARTTLS option specifies whether to use Tunneled Transport Layer Security
( TTLS ) mode at startup or when needed.
The SASL_POLICY_NOANONYMOUS option specifies whether Simple Authentica-
tion and Security Layer ( SASL ) mechanisms, which accept anonymous logins, are
permitted.
Finally, since our security realm also included an authentication security domain, we
can choose to restrict access to some methods by specifying a @RolesAllowed
annotation, which requires the role ejbRole :
@RolesAllowed("ejbRole")
public String bookSeat(int se;atId) throws
SeatBookedException {