Have you correctly defined the Jboss realm for the web-app in a
jboss-web.xml file?
java:/jaas/YourSecurityDomain
-Mensaje original-
De: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] En nombre de
Benjamin Brown
Enviado el: jueves, 20 de julio de 2006 13:23
Para: acegisecurity-deve
First of all I'll try to clarify what I understand for the problem you
propose.
A- Client calls remote method getAccount
B- Client application gets serialized version of Account object
C- Client modifies local unserialized account Object
D- Client serializes and sends the modified account object
Andy,
I agree that filtering the method response is a fascinating area. The only
problem I have always found on filtering a method response is that it
doesn't scale properly when performance is an issue. I'm particularly
thinking on Collections here, where the full collection check for
permission
wards Aceg Security
official1.0.0 release
Sergio Berna wrote:
>
>I have added ExpirationDetails as a separate interface to keep backwards
>compatibility with existing code that implementes UserDetails.
>
>
>
>
Hi Sergio
Good to see backward compatibility is a priority, par
Ben,
What do you mean by container integration deprecation?
Does it mean that the adapters package will dissapear in a next future or
do you plan to move them to a sort of components sandbox?
Sergio.
-Mensaje original-
De: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] En nombre de
Ben Ale
Ben,
Finally I have jaas CredentialsExpiredException and
AccountExpiredException working under acegi security integrated in JBoss
container.
The modifications on acegi were quite simple.
First I have created 2 new Exceptions named:
net.sf.acegisecurity.AccountExpiredException
net.sf.acegisecuri
