Why does the "other" security-domain get called instead of the security domain specified in the @SecurityDomain annotation in JBoss 5?
Issue
We have a bean/ws with JBoss @context annotation that maps to a JAAS domain in the login-config.xml file. But what we and have noticed is that in EAP 5.2 the right domain (@SecurityDomain(value = "ImaSecurityDomain") is not getting called, instead every thing got delegated to the default "other" domain even though this code has been working fine in EAP 4.3. Has any thing changed in EAP 5.2, that we are not aware of, or is there any configuration setting we are missing some where?
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 5.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
