Differences between revisions 1 and 8 (spanning 7 versions)

JBoss

Application server that implements the Java Platform, Enterprise Edition (Java EE) http://en.wikipedia.org/wiki/Jboss.

Message driven bean (JBoss)

A message-driven bean is an enterprise bean that allows J2EE applications to process messages asynchronously.

https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/5/html/Messaging_User_Guide/ch05s13.html#table-MDB_JCA_Spec_Properties

Annotations, MDB Properties Provided by the JCA Specification

Name	Type	Default value	Remarks
destination	java.lang.String	none	This property is Mandatory The JNDI name of the Queue or Topic.
destinationType	java.lang.String	none	The type of destination valid values are javax.jms.Queue or javax.jms.Topic
messageSelector	java.lang.String	none	The message selector of the subscription
acknowledgeMode	int	AUTO_ACKNOWLEDGE	The type of acknowledgement when not using transacted jms - valid values AUTO_ ACKNOWLEDGE or DUPS_OK_ ACKNOWLEDGE
clientID	java.lang.String		The client id of the connection
subscriptionDurability	String	NonDurable	Whether topic subscriptions are durable. Valid values are Durable or NonDurable

||subscriptionName||String||none||The subscription name of the topic subscription||

MDB Properties Provided as JBoss Extensions

Name	Type	Default value	Remarks
isTopic	boolean	false	Sets the destinationType
providerAdapterJNDI	java.lang.String	DefaultJMSProvider	The JNDI name of the JMS provider.
user	java.lang.String	none	The user ID used to connect to the JMS server
pass	java.lang.String	none	The password of the user
maxMessages	int	1	Read this number of messages before delivering messages to the MDB. Each message is delivered individually on the same thread in an attempt to avoid context excessive context switching
minSession	int	1	The minimum number of JMS sessions that are available to concurrently deliver messages to this mdb
maxSession	int	15	The maximum number of JMS sessions that are available to concurrently deliver messages to this mdb
reconnectInterval	long	10 seconds	The length of time in seconds between attempts to (re-)connect to the JMS provider
keepAlive	long	60 seconds	The length of time in milliseconds that sessions over the minimum are kept alive
sessionTransacted	boolean	true	Whether the sessions are transacted
useDLQ	boolean	true	Whether to use a Dead Letter Queue (DLQ) handler.
dLQJNDIName	java.lang.String	queue/DLQ	The JNDI name of the DLQ
dLQHandler	java.lang.String	org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler	The org.jboss.resource. adapter.jms.inflow. DLQHandler implementation class name.
dLQUser	java.lang.String	none	The user id used to make the dlq connection to the JMS server
dLQPassword	java.lang.String	none	The password of the dLQUser
dLQClientID	java.lang.String	none	The client id of the DLQ connection
dLQMaxResent	int	5	The maximum number of times a message is redelivered before it is sent to the DLQ.
redeliverUnspecified	boolean	true	Whether to attempt to redeliver a message in an unspecified transaction context
transactionTimeout	int	Default is the timeout set for the resource manager	Time in seconds for the transaction timeout
DeliveryActive	boolean	true	Whether the MDB should make the subscription at initial deployment or wait for start() or stopDelivery() on the corresponding MBean. You can set this to false if you want to prevent messages from being delivered to the MDB (which is still starting) during server start up.

Timers annotations

Creating Calendar-Based Timer Expressions http://docs.oracle.com/cd/E19226-01/820-7627/giqlk/index.html

Examples:

Every five minutes, @Schedule(minute = "*/5" , hour="*")
Every twenty minutes from 5 to 21, @Schedule(minute="*/20" , hour = "5-21")
At one AM, @Schedule(hour = "1")
At two AM and five PM, @Schedule(hour = "2,17")

JAAS security JBoss AS7

JAAS (Java Authentication and Authorization Service).

Read http://amatya.net/blog/implementing-security-with-jaas-in-jboss-as-7/

Basic authentication Web application

Add user and roles:

/opt/jboss-as-7.1.1.Final/bin/add-user.sh -a userx passx # add user userx
Files /opt/jboss-as-7.1.1.Final/standalone/application-users.properties and /opt/jboss-as-7.1.1.Final/domain/application-users.properties changed
vi /opt/jboss-as-7.1.1.Final/standalone/application-roles.properties # add primary role
userx=AppXYZUser # in application-roles.properties

Edit web.xml file for the web application:

   1 <web-app>
   2 <!-- other stuff .....-->
   3     <!-- security application realm -->
   4     <security-constraint>
   5         <web-resource-collection>
   6             <web-resource-name>HtmlAuth</web-resource-name>
   7             <description>application security constraints</description>
   8             <url-pattern>/*</url-pattern>
   9             <http-method>GET</http-method>
  10             <http-method>POST</http-method>
  11         </web-resource-collection>
  12         <auth-constraint>
  13             <role-name>AppXYZUser</role-name>
  14         </auth-constraint>
  15     </security-constraint>
  16     <login-config>
  17         <auth-method>BASIC</auth-method>
  18         <realm-name>ApplicationRealm</realm-name>
  19     </login-config>
  20     <security-role>
  21         <role-name>AppXYZUser</role-name>
  22     </security-role>    
  23     <!-- security application realm -->
  24 </web-app>

Edit jboss-web.xml

   1 <?xml version="1.0" encoding="UTF-8"?>
   2 <jboss-web>
   3   <context-root>/AppContextRoot</context-root>
   4   <security-domain>java:/jaas/other</security-domain> <!-- security application realm -->
   5 </jboss-web>

Forms login

In web.xml:

   1     <login-config>
   2         <auth-method>FORM</auth-method>
   3         <realm-name>AppRealm</realm-name>
   4         <form-login-config>
   5             <form-login-page>/login.html</form-login-page>
   6             <form-error-page>/error.html</form-error-page>
   7         </form-login-config>
   8     </login-config>

JDBC authentication

For this setup the password is in plain text ! It must be improved in order to use hash like MD5 or SHA1.

Create tables on a PostgreSQL server:

psql -U userx -W -d databasex -h 192.168.1.1
\c databasex
create table users (username varchar(128) NOT NULL,password varchar(128) NOT NULL );
create table roles (username varchar(128) NOT NULL,role varchar(128) NOT NULL );
insert into users (username,password) values('userx1','12345678');
insert into roles (username,role) values('userx1','User');
insert into roles (username,role) values('userx1','UserManager');
grant all privileges on database dldserver to dldserver;
alter table users owner to userx;
alter table roles owner to userx;

Add security domain to standalone-full.xml:

   1 <security-domain name="jdbcRealm" cache-type="default">
   2  <authentication>
   3   <login-module code="Database" flag="required">
   4    <module-option name="dsJndiName" value="java:jboss/datasources/ServerDS"/>
   5    <module-option name="principalsQuery" value="SELECT password FROM users WHERE username=?"/>
   6    <module-option name="rolesQuery" value="SELECT role, 'Roles' FROM roles WHERE username=?"/>
   7    <module-option name="unauthenticatedIdentity" value="guest"/>
   8   </login-module>
   9  </authentication>
  10 </security-domain>

Alter jboss-web.xml:

   1 <jboss-web>
   2 <!-- ... -->
   3     <security-domain>java:/jaas/jdbcRealm</security-domain>
   4 </jboss-web>

-  ⇤ ← Revision 1 as of 2013-07-16 15:14:36 → 
  Size: 1350
  Editor: bl13-255-137
  Comment:
+   ← Revision 8 as of 2013-08-22 16:58:34 → ⇥
  Size: 7835
  Editor: bl13-30-44
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 20:
+=== MDB Properties Provided as JBoss Extensions ===

||Name||Type||Default value||Remarks||
||isTopic||boolean||false||Sets the destinationType||
||providerAdapterJNDI||java.lang.String||DefaultJMSProvider||The JNDI name of the JMS provider.||
||user||java.lang.String||none||The user ID used to connect to the JMS server||
||pass||java.lang.String||none||The password of the user||
||maxMessages||int||1||Read this number of messages before delivering messages to the MDB. Each message is delivered individually on the same thread in an attempt to avoid context excessive context switching||
||minSession||int||1||The minimum number of JMS sessions that are available to concurrently deliver messages to this mdb||
||maxSession||int||15||The maximum number of JMS sessions that are available to concurrently deliver messages to this mdb||
||reconnectInterval||long||10 seconds||The length of time in seconds between attempts to (re-)connect to the JMS provider||
||keepAlive||long||60 seconds||The length of time in milliseconds that sessions over the minimum are kept alive||
||sessionTransacted||boolean||true||Whether the sessions are transacted||
||useDLQ||boolean||true||Whether to use a Dead Letter Queue (DLQ) handler.||
||dLQJNDIName||java.lang.String||queue/DLQ||The JNDI name of the DLQ||
||dLQHandler||java.lang.String||org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler||The org.jboss.resource. adapter.jms.inflow. DLQHandler implementation class name.||
||dLQUser||java.lang.String||none||The user id used to make the dlq connection to the JMS server||
||dLQPassword||java.lang.String||none||The password of the dLQUser||
||dLQClientID||java.lang.String||none||The client id of the DLQ connection||
||dLQMaxResent||int||5||The maximum number of times a message is redelivered before it is sent to the DLQ.||
||redeliverUnspecified||boolean||true||Whether to attempt to redeliver a message in an unspecified transaction context||
||transactionTimeout||int||Default is the timeout set for the resource manager||Time in seconds for the transaction timeout||
||DeliveryActive||boolean||true||Whether the MDB should make the subscription at initial deployment or wait for start() or stopDelivery() on the corresponding MBean. You can set this to false if you want to prevent messages from being delivered to the MDB (which is still starting) during server start up. ||

== Timers annotations ==
Creating Calendar-Based Timer Expressions
[[http://docs.oracle.com/cd/E19226-01/820-7627/giqlk/index.html]]

Examples:
 * Every five minutes, '''@Schedule(minute = "*/5" , hour="*")'''
 * Every twenty minutes from 5 to 21, '''@Schedule(minute="*/20" , hour = "5-21")'''
 * At one AM, '''@Schedule(hour = "1")'''
 * At two AM and five PM, '''@Schedule(hour = "2,17")'''

== JAAS security JBoss AS7 ==
JAAS (Java Authentication and Authorization Service).

Read [[http://amatya.net/blog/implementing-security-with-jaas-in-jboss-as-7/]]

=== Basic authentication Web application ===
Add user and roles:
 * /opt/jboss-as-7.1.1.Final/bin/add-user.sh -a userx passx # add user userx
 * Files  /opt/jboss-as-7.1.1.Final/standalone/application-users.properties  and /opt/jboss-as-7.1.1.Final/domain/application-users.properties  changed
 * vi /opt/jboss-as-7.1.1.Final/standalone/application-roles.properties # add primary role 
 * userx=AppXYZUser # in application-roles.properties

Edit web.xml file for the web application:
{{{#!highlight xml
<web-app>
<!-- other stuff .....-->
    <!-- security application realm -->
    <security-constraint>
        <web-resource-collection>
            <web-resource-name>HtmlAuth</web-resource-name>
            <description>application security constraints</description>
            <url-pattern>/*</url-pattern>
            <http-method>GET</http-method>
            <http-method>POST</http-method>
        </web-resource-collection>
        <auth-constraint>
            <role-name>AppXYZUser</role-name>
        </auth-constraint>
    </security-constraint>
    <login-config>
        <auth-method>BASIC</auth-method>
        <realm-name>ApplicationRealm</realm-name>
    </login-config>
    <security-role>
        <role-name>AppXYZUser</role-name>
    </security-role>    
    <!-- security application realm -->
</web-app>
}}}

Edit jboss-web.xml
{{{#!highlight xml
<?xml version="1.0" encoding="UTF-8"?>
<jboss-web>
  <context-root>/AppContextRoot</context-root>
  <security-domain>java:/jaas/other</security-domain> <!-- security application realm -->
</jboss-web>
}}}

== Forms login ==
In web.xml:
{{{#!highlight xml
    <login-config>
        <auth-method>FORM</auth-method>
        <realm-name>AppRealm</realm-name>
        <form-login-config>
            <form-login-page>/login.html</form-login-page>
            <form-error-page>/error.html</form-error-page>
        </form-login-config>
    </login-config>        
}}}
 
== JDBC authentication ==
For this setup the password is in plain text !
It must be improved in order to use hash like MD5 or SHA1.

Create tables on a PostgreSQL server:
 * psql -U userx -W -d databasex -h 192.168.1.1
 * \c databasex
 * create table users (username varchar(128) NOT NULL,password varchar(128) NOT NULL );
 * create table roles (username varchar(128) NOT NULL,role varchar(128) NOT NULL );
 * insert into users (username,password) values('userx1','12345678');
 * insert into roles (username,role) values('userx1','User');
 * insert into roles (username,role) values('userx1','UserManager');
 * grant all privileges on database dldserver to dldserver;
 * alter table users owner to userx;
 * alter table roles owner to userx;

Add security domain to standalone-full.xml:
{{{#!highlight xml
<security-domain name="jdbcRealm" cache-type="default">
 <authentication>
  <login-module code="Database" flag="required">
   <module-option name="dsJndiName" value="java:jboss/datasources/ServerDS"/>
   <module-option name="principalsQuery" value="SELECT password FROM users WHERE username=?"/>
   <module-option name="rolesQuery" value="SELECT role, 'Roles' FROM roles WHERE username=?"/>
   <module-option name="unauthenticatedIdentity" value="guest"/>
  </login-module>
 </authentication>
</security-domain>
}}}

Alter jboss-web.xml:
{{{#!highlight xml
<jboss-web>
<!-- ... -->
    <security-domain>java:/jaas/jdbcRealm</security-domain>
</jboss-web>
}}}