Title: Message
I'm new to Acegi
Security and I'm evaluating how it works and at the moment I'm not finding a way
to declare method-level security with differing parameters. Is this
possible with Acegi Security? To attempt to make my question
clearer, here is an XML snippet of what I'm att
complicate things, you may just want to break the method
into 2: createBusinessAccount and createConsumerAccount since you
obviously have different business rules regarding them.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Doody, John
TED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Doody, John
Sent: Wednesday, April 27, 2005 7:53 AM
To: [EMAIL PROTECTED]
Subject: [Acegisecurity-developer] RE: Securing methods to the parameter
level
Yes, we already thought about distinct methods. However, is this
possible with Acegi?
Title: Message
It looks
like the BasicAclEntryVoter source is a
good starting place for creating the voter we need. It uses Reflection to
examine the parameter types passed into a method. Thanks for all the help.
Title: Message
I'm
attemping to intercept a method call using the
net.sf.acegisecurity.intercept.method.aopalliance.MethodSecurityInterceptor
bean. Unfortunately the method does not seem to get
intercepted. My user has a role of ROLE_ANONYMOUS and gets
authenticated successfully via InMe
Title: Message
I'm working on a
project and we are looking to use Acegi Security. Our J2EE container
will be a WebLogic (WLS) clustered architecture. From my research
thus far, it looks like I will not have to worry about hitting the same WLS
instance where a user authenticated (IP Sticky
Title: Message
George,
Thanks for the
test. I'll double check my method call names. Also, thanks for the
responce to the other post regarding IP Stickyness.
John
