Migrating to 5.1.0, "Invalid User"-Exception

[gupta]

We are currently in a process of migrating our AS from JBoss 4.2.1 to JBoss 5.1.0. We keep getting "Invalid User"-Exceptions thrown in our test classes due to thread issues with the JBoss implementation. Apparently (as far as wecan tell) it seem to do with the fact that we spawn a new thread in the beginning of each test case, where we do the log in.

In our main program (the non-test classes) however JBoss 5 works fine, since the log-in process in that case is made in the UI-thread (from the log-in dialog).

We've also figured it had to do with the SecurityInterceptors and tried to shut them down, without success. What about 'Subject.doAs'in the new JBoss 5, is it needed at all or is it handled by the interceptors in the proxy? If so, how may we control the interceptors?

Anyone who has a clue!?

Thanks in advance

/Gupta

[wolfgangknauf]

Hi,

does this help?
https://jira.jboss.org/jira/browse/SECURITY-272
According to this, you have to add one parameter to "auth.conf".

Best regards

Wolfgang

[gupta]

"Wolfgang Knauf" wrote:
Hi,

does this help?
https://jira.jboss.org/jira/browse/SECURITY-272
According to this, you have to add one parameter to "auth.conf".

Best regards

Wolfgang

Unfortunately, we tried this already without success. We have also tried using the following VM-arguments:


org.jboss.security.SecurityAssociation.ThreadLocal
org.jboss.security.context.ThreadLocal


To true/false respectively. They all change the behaviour of SecurityAssociation, but the problem still remains since the log in is made in a separate thread.

BR,
Gupta

[wolfgangknauf]

Hi,

sorry, but then I cannot help further.

Any chance to change your test class, so that the login is in the main thread or in each thread?

Best regards

Wolfgang

[gupta]

We're currently in the process of rewriting our tests right now. Seems to be the most efficient way at the moment. Thanks anyway for your help!!

/Gupta