Vikas Sasidharan wrote:
I am not so enthusiastic about setting the flag to true. Could anybody
suggest some other possible alternatives? My last option is to have a
custom MethodSecurityInterceptor that enables separation of
before-invocation and after-invocation interception.
The problem is
Hi All,
I have my server whose APIs are exposed via RMI, RMI-IIOP. For a normal
RMI client, context can be easily passed from the client by using
ContextPropagatingRemoteInvocationFactory
and the following lines of code:
Authentication authRequest = new
I'm using RC-2 and I think I'm having trouble with the IllegalStateException problem as detailed in SEC-211. It appears
that this issue is fixed in CVS, but won't be in a release until 1.0 final. Wondering if you guys are close on final
(like in the next week or so), or if I should use a nightly
Ben Munat wrote:
I'm using RC-2 and I think I'm having trouble with the
IllegalStateException problem as detailed in SEC-211. It appears that
this issue is fixed in CVS, but won't be in a release until 1.0 final.
Wondering if you guys are close on final (like in the next week or
so), or if I
Richard Han wrote:
My question probably is more suitable to user-list, but we don't have one.
Anyway, I am new to acegi, my question is, how do you customize role names,
for instance, if I want to use ROLE_STUDENT, ROLE_PROFESSOR, how would I let
acegi recognize them?
In two places:
1.
Thanks for your quick reply!
I am using daoAuthenticationProvider, and didn't find UserDetailsService
property you mentioned (btw, I'm trying out acegi-0.9.0).
Also, I guess I need to create records in autorities table, right? I wish
acegi has a roles table, (and a group table).
-Original
Sweet! That's wonderful news. I'll hold off on updating until then.
Thanks,
b
Ben Alex wrote:
Ben Munat wrote:
I'm using RC-2 and I think I'm having trouble with the
IllegalStateException problem as detailed in SEC-211. It appears that
this issue is fixed in CVS, but won't be in a release
