Just found that it does not work at all with a policy in jboss-app.xml.
Apparently it is used to authenticate accesses to the ejb module even though
they come from an already authenticated web application.
My new and improved question is thus;
Is it at all possible to two web modules in one ea
Hi,
We have an EAR that contains two web modules and one ejb module. The two web
modules need to use different application policies declared in logon-config.xml.
In an earlier version of out application, one policy was sufficient and it
could be specified in jboss-app.xml.
The first thing I tr
"[EMAIL PROTECTED]" wrote : Because classes used by the ejbs are duplicately
deployed in the war.
Yepp, that was it. Two libraries that were included in the EAR, on the same
level as the WAR, were also in the WEB-INF/lib inside the WAR. A relic from the
time when the application was just a WAR
Thanks, now I think I get it perhaps. Seems like JBoss has choosen a different
path to allow the deployer to map application roles to domain roles. Instead of
doing it in the deployment descriptor, like Sun and BEA does it, the
application role names are known and provided by the login module. T
Yes, it makes sense but it doesn't solve my problem. Perhaps I'm going about it
the wrong way. What I want to acheive is this:
In my security domain I want to specify that the user "gugrim" is an "admin".
In one application I use a role name like "Admin"
Yes I have, in jboss-app.xml. It points to the "other" domain. The user gets
the roles according to the roles.properties. What I want to achieve is to use
different role names in the application than the ones defined for the domain,
and map the application roles to domain roles using tags.
Gun
Thanks Scott, but I've read that, and the article it refers to, and I don't
think it applies to my problem. Only one application is involved and all
libraries it uses (except the JRE) are included in the EAR, so I can't see any
reason why the page controller in the WAR should be loaded by anothe
Hi!
I'm trying to call a local session bean from a JSP page and get the error:
javax.ejb.EJBException: Invalid invocation, check your deployment packaging
The JSP is contained in a WAR, the session bean in an EJB JAR, all of it
packaged in an EAR.
The page successfully looks up the home interf
I have now found how to get the JAAS service to log at trace level and found
the most basic problem:
I my login-config.xml I had placed the module options outside the
tag instead of inside.
I have also found that if I put real application role names, such as "Users" in
the "roles.properties",
-----
~/jboss-4.0.3SP1/server/default/conf/props/users.properties:
gugrim=password
----
~/jb
10 matches
Mail list logo
