Then that is an ejb3 bug.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3954032#3954032
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3954032
Using Tomcat but need to do more? Need to support web services, security?
Get
[EMAIL PROTECTED] wrote : Then that is an ejb3 bug.
Does this mean that you'll be reverting back to using java:/jaas/ in
jboss.xml (or @SecurityDomain) in a future version?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3954041#3954041
Reply to the post :
That problem had me stuck for quite a while. It's especially tough as all the
tutorials and JaasHowTo and JASS FAQ don't mention this issue.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3954088#3954088
Reply to the post :
cgriffith, I'm pretty much following the same configuration procedures that I
have for all previous versions of jBoss. I simply put my application-policy's
XML snippet into the login-config file. Usually after, the JAAS JNDI entry
shows up in the JNDIView and is accessible by my security-domain
OK, aside from a reinstall, I'm not sure what I did differently, but I now get
this error. It happens on first access of the application. This means that
deployment is happening correctly, but that for some reason it is either using
the default realm or ignoring the DatabaseServiceLoginModule.
Oh, and here is the trace leading up to the error. It's as if jBoss is ignoring
the security domain entries in jboss-web.xml and jboss.xml.
anonymous wrote : 2006-06-27 10:12:06,082 TRACE
[org.jboss.security.SecurityAssociation] pushRunAsIdentity, runAs=null
| 2006-06-27 10:12:06,082 TRACE
David,
Yes, your login-config.xml is correct. Your earlier post varifies that the
PinkRealm is in fact getting configured. The problem is with your
deployment. The output from your last post shows that the a java:
security-domain is being attempted, but since it does not exist, the default
To get the security domain settings I'm using jboss-web.xml and jboss.xml just
as I did in 4.0.3. There is nothing peculiar about them. And if I try to use
the @SecurityDomain annotation instead, I get the same problem. Here are the
files ...
?xml version=1.0 encoding=UTF-8?
!DOCTYPE
David,
I have a good look at the trace logging when you deploy your ear. Look for
security-domain binding settings made by deployer and parsing of your
descriptors.
cgriffith
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3953743#3953743
Reply to the post :
Also,
Doing a forum search with query @SecurityDomain AND annotation AND security
domain yeilds similar situations as yours.
cgriffith
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3953751#3953751
Reply to the post :
This is what I have for parsing of the jboss.xml file. Not much in the line of
tracing ...
2006-06-27 11:14:30,834 DEBUG [org.jboss.ejb3.Ejb3Module] Creating
jboss.j2ee:service=EJB3,module=pinkcommon-ejb.jar
2006-06-27 11:14:30,841 DEBUG [org.jboss.ejb3.security.JaccHelper] Initialising
JACC
This thread has the answer.
http://www.jboss.com/index.html?module=bbop=viewtopict=78329
Apparently, the java:/jaas/ must now be removed. Not that this is your fault,
but it would have been nice if this change have been documented in the release
notes. It's a pretty significant change.
Now, I
Actually, it gets even weirder. It is true that you need to remove
java:/jaas/ in jboss.xml 's security-domain element. But that same prefix
must be present in the jboss-web.xml 's security-domain element otherwise the
web authentication doesn't work.
View the original post :
David,
One thing I noticed is you forgot the authentication element (or maybe you just
did not post it.) See the login-config.xml file for xml elements.
cgriffith
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3953446#3953446
Reply to the post :
Enable trace logging as highlighted in the FAQ at the beginning of this forum.
You will see if there are any parsing issues with your login config file.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3953448#3953448
Reply to the post :
j2ee_junkie, I must have done something wrong when creating the post, because
the terminating element is in there.
anil, below is the relevant trace information. It looks like it loads OK.
anonymous wrote : 2006-06-26 11:05:15,553 DEBUG
[org.jboss.security.auth.login.XMLLoginConfigImpl] Try
disable html and post your loginConfig.xml
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3953471#3953471
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3953471
Using Tomcat but need to do more? Need to support web services,
Here you go ...
?xml version='1.0'?
!DOCTYPE policy PUBLIC
-//JBoss//DTD JBOSS Security Config 3.0//EN
http://www.jboss.org/j2ee/dtd/security_config.dtd;
!-- The XML based JAAS login configuration read by the
org.jboss.security.auth.login.XMLLoginConfig mbean. Add
an
looking good.
can you please post your jboss_app.xml or jboos_web.xml that reference the
security-domain?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3953493#3953493
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3953493
tefron, I've entries in jboss.xml and jboss-web.xml.
Here's jboss.xml
?xml version=1.0 encoding=ISO-8859-1 ?
!DOCTYPE jboss PUBLIC
-//JBoss//DTD JBOSS 4.0//EN
http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd;
security-domainjava:/jaas/PinkRealm/security-domain
And here's
try and add the security-domain to your jboss-app.xml.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3953509#3953509
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3953509
Using Tomcat but need to do more? Need to support
That did not help. That said, I don't think the problem is with the
security-domain elements. I believe that for some unexplainable reason my
JAAS PinkRealm is not being created. I base that on the fact that when I invoke
the JNDIView tree, it doesn't show with the JAAS services.
I've
David,
Set trace logging for the security layer. Then restart the server, and look
for output from the config service when it is starting. Post any details.
later, cgriffith
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3953521#3953521
Reply to the post :
whoops. I see Anil already suggested that now. sorry. Will get back with you.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3953523#3953523
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3953523
Using Tomcat but need to
David,
I see that only some of the application-policies are being deployed. Did you
post a different login-config.xml than the one used when posting JNDI view? If
not then look at the trace log again during XMLLoginConfigIml service startup.
This time post all application-policy
25 matches
Mail list logo
