Hi Wolfgang and Anil

Thank you for your replies. I changed the client login as mentioned in the thread:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=144865]

Unfortunately, it didn't solve the problem. May the problem is related to how my custom login module passes the roles back to the JAAS framework. According this blog:
http://stuffthathappens.com/blog/2008/05/16/writing-a-custom-jaas-loginmodule/]
the way of passing roles are JBoss specific. May I have to pass it differently when using standard JAAS client login without the SecurityClient.

The code is:

if (!subject.getPrincipals().contains(user))
{
 subject.getPrincipals().add(user);

 /**
 * this is the important part to work with JBoss:
 * jboss requires the name 'Roles'
 */
 SimpleGroup group = new SimpleGroup("Roles");
 for (SimplePrincipal role : roles)
 {
 group.addMember(role);
 }

 subject.getPrincipals().add(group);
}

Yes, I am aware of it. May I was not precise enough. Everything works fine except that the roles are not propagated to the EJB module. The code I added in the previous message is a snippet from the custom login module running in JBoss. Again, it works with using SecurityClient and works not when using standard JAAS client login.