kgoedert,
You haven't yet posted any code or configurations, so i don't exactly know what
might be wrong :-)
Sometime back, there was a similar thread where we had a discussion about
securing EJBs and allowing only specific roles to have access to the methods.
Read through this thread
Thanks for your time. I figured out how to do this. I had some concepts
misunderstood. My login-config.xml had some extra configurations that should
not be there.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4164483#4164483
Reply to the post :
Please post the entire exception stacktrace, your code and the custom login
configuration. Which version of JBoss and Java are you using?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4164257#4164257
Reply to the post :
Hi,
I guess I solved part of my problem by removing the security domain
configuration I had on my jboss.xml. My understanding was that when I looked up
a bean my application was initiating a new login process instead of using the
one that was returned when I called the login method explicitly
My understanding was totally wrong. Doing what I described in the last post
logged me in as an anonymous user.
How should I look up a bean after login() in LoginContext succeeds?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4164298#4164298
Reply to the post
