I have read many topics on the forums about this, but it seems that I can't get
it work right. Here is my code:
java.util.ArrayList servers=MBeanServerFactory.findMBeanServer(null);
| if (servers.size() != 1)
| System.out.println(uh-oh, etc);
| MBeanServer mbeanServer = (MBeanServer)
I forgot to mention that I use JBOSS 3.2.5 in case it makes a difference.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3893596#3893596
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3893596
ProxyLoginModule was the answer, I found it re-reading the admin-develop docs.
Cheers
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3857139#3857139
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3857139
Unfortunately that didn't solve the problem. I thought everything was fine when
I discovered about the ProxyLoginModule but in fact the classloader is still
looking for server side classes the client should not have access to nor care
about...
If I include jboss_dist/server/all/lib/jbosssx.jar
Try to put the ClientLoginModule as the last module in your config file.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3857168#3857168
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3857168
I finally got it right. I was doing almost everything right
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3857176#3857176
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3857176
This is indeed what I was thingking but then I don't quite understand why the
client needs it to work. Probably a mistake on my part but I don't know where.
I simply inherited from that class following other JAAS examples to create my
custom login module, nothing more.
I'll look in my code.
When running my application (swing) I get this error:
java.lang.NoClassDefFoundError:
org/jboss/security/auth/spi/AbstractServerLoginModule
This happens when I try to login. I am using a custom login module that extends
the AbstractSLM, maybe I did some mistake configuring the application? It
Darknight wrote : It works if I include the jars in /server/myconfig but it
doesn't if I only include those in /client and /lib
|
I ment put in classpath not include, that way it looks like a compiler
problem.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp
Thank you for replying.
I have investigated more and I assume that the security cache timeout occurs
even if the authed client makes access to one bean while another is inactive, I
still have to be sure about this and will try to look in the cache with JMX
console.
And yes, the already logged
Maybe, but unfortunately the times do not coincide. I have set
DefaultCacheTimeout to 300 via JMX console and the problem still occurs after
20-30 minutes.
Right now I'm trying to find a different route to solve the problem since I
can't track it's root (namely, I'm toying with my custom
That worked!
As soon as the cache expires the client is kicked from jboss.
So I have narrowed the problem and will go on trying to fix it.
My question is: why a cache? Or rather, why do you need to re-auth after some
time? I think this is related to web sessions and the like and makes little
I gave up on modifying the loginmodule, I circumvented the problem this way:
the client will perform a mandatory post-create initialization which will
perform all additional required checks.
It seemed cleaner to me to perform every check in one place but it turned out
far too difficult and
I have a client that has access to jboss/EJB and performs auth via JAAS.
Periodically the client makes remote calls, about every 30 seconds. What
happens is that after some time the login data seems to be lost and the
client needs to re-auth, however the way the login module works makes
this
tthiele wrote : The ClientLoginModule places the principals and credentials which
are aquired by the previous login module(s) in a magic way to a magic place where bean
invocation mechanism passes them to the container resp. beans. I suppose the security
information is associated with the
I have the very same problem even if my code does something different. Server-side the
data source IS bound...
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3849387#3849387
Reply to the post :
And the answer is: you cannot access the DS from client...
So make a bean to handle it.
However, since the default behaviour for JAAS login modules is to make a direct query
on the DS it was AWFULLY strange that it didn't work. This isn't coherent at all,
please rectify this in the jaas
I have added my own DS to my jboss installation, when I tried it with ejbs it seemed
to work, also it appears in the web console and is listed at startup among the
deployed stuff.
Now I'm using it with JAAS and I get this error:
Login failed
| javax.security.auth.login.LoginException:
When a client disconnects (goes offline, crashes, etc) from jboss, what are the
effects?
Is it the same as if it had called remove() and then logged out? Immediately or there
is a delay of some sort?
What kind of behaviour should I expect?
Thanks
View the original post :
You are right: the client was using a stateful session bean (directly) and stateless
session beans (indirectly by means of the session bean).
The client should have logged in by means of the appropriate jboss extension.
View the original post :
Alex I suggest you to find an alternative design for your interaction. Strongly.
I tried but I found no RELIABLE way. Every solution has more disadvantages then
advantages, the only practical thing to do is to actively poll the ejb.
View the original post :
I'm very new to jboss and I'm still reading documentation.
It is critical for my application that my stateful session bean knows the client ip.
From what I have read until now it seems that this is not possible in a direct way
(feature request incoming...).
That said, if I'm right about the
22 matches
Mail list logo
