JBoss Migration
Security changes
JBoss application security is configured via JAAS login configuration. The XML based file is located at ~myserver/conf/login-config.xml
Add an application-policy element for each security domain. For this exercise we added the following entry:
<application-policy name="jmsconsole">
<authentication>
<login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag="required">
<module-option name="usersProperties">props/jmsconsole-users.properties</module-option>
<module-option name="rolesProperties">props/jmsconsole-roles.properties</module-option>
</login-module>
</authentication>
</application-policy>
The users and the role definition and the mapping between users and roles are configured in the usersProperties and rolesProperties.
The policy name jmsconsole would be referred in the jboss-web.xml file.
<jboss-web>
<security-domain>
java:/jaas/jmsconsole
</security-domain>
</jboss-web>
JMS changes
WebLogic Error Destination and JBoss DLQ.
Once WebLogic JMS fails to redeliver a message to a destination for a specific number of times, the message can be redirected to an error destination that is associated to the message destination. How to configure Error Destinations in WebLogic
In JBoss the same concept is achieved by configuring the Dead Letter Queue.
How to configure DLQ in JBoss
This is a nice article sir,
Excellent
Thank you so much
great help for newbee’s
Hi Rahul. I am facing an issue with on of our app which has been migrated from Weblogic to JBOSS.
This is the issue:
The application has two user-roles:
1. Admin
2. Normal User
Firstly,an admin logs in,he is able to work fine with his privileges.
Secondly,a normal user logs in and he is able to work fine with his respective privileges.
Thirldy,when an admin logs in,his privileges have been set as of a normal-user.The buttons which were generally enabled for him have been disabled.
Rest of the application is working fine.
This problem persists until we restart the servers.And if a normal user logs in,the issue persists.
As of now,as a work-around,we have requested the normal users not to login into the application.
Note:
1.The JDK has been upgraded from 1.4 to 1.6
2.Oracle has been upgraded from 9i to 11G.
We do not know whether the issue is with code or the configuration settings of JBOSS server.
The log files are not showing any errors.
If you can help me,please contact me on my mai:
ainkollu@gmail.com
I could not send a mail to your mail ragrawal@xebia.com