I think my role mapping question is basically answered by this thread:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=77709
Seems like I'll have to do this mapping myself, as the spec is not clear on
this.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtop
I'm glad you solved the roles problem in your configuration.
With this configuration, you are mapping your groups in LDAP directly to the
security roles configured in your JBoss deployments. This means that you are
effectively using the same group / role names.
Does anyone know if it's possibl
Hi,
Although there are a couple of things still unclear to me in the Tomcat
environment, I got this working.
I don't really need this, but I battled to get it working by implementing a
Tomcat Valve. I guess it has to do with the order in which Tomcat invokes the
configured valves, but in my V
I appreciate the quick response.
You've put me on the right track now. I'll play around with the
above-mentioned concepts and post my findings again.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3928754#3928754
Reply to the post :
http://www.jboss.com/ind
Hi,
Could someone please clarify this for me?
I've got the following situation:
Standalone standard Tomcat 4.1.29 with a couple of secured pages and FORM based
login.
I'm using the JAASRealm in Tomcat to perform authentication through JAAS. As
part of this authentication, I'm using my own Logi
I had exactly the same problem, although I built my example application with
Maven.
In my case, when I looked at the server.log debug statements, it pointed out
that Seam cannot find my components:
| 2006-02-16 16:36:28,312 DEBUG [org.jboss.seam.jsf.SeamVariableResolver]
resolving name: use
anonymous wrote :
| Did you change the default log4j settings, because in your server startup
log, I don't see any of the EJB3Trail beans being deployed?
|
You should also maybe confirm that you installed the 4.0.4RC1 server with EJB3
support..
View the original post :
http://www.jboss.c
I downloaded the EJB3Trail source code end of last week, compiled locally and
successfully deployed on 4.0.4RC1.
Did you change the default log4j settings, because in your server startup log,
I don't see any of the EJB3Trail beans being deployed?
View the original post :
http://www.jboss.com/i
Suppose you have figured it out by now, but you could always query the 'Port'
attribute of the 'jboss:service=HAJNDI' MBean through the local MBeanServer.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865159#3865159
Reply to the post :
http://www.jboss.org/
