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
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
Ben,
Excellent, sounds like a well thought-out plan towards 1.0.
I'd recommend an in-between approach for the container adapters. I
agree that including lightly-used, non-portable modules in the main
distribution can lead to expectations that they be maintained as fully as the
core.
Hello list!
I'm planning to write a MSc thesis on the subject of business tier
security. My idea was to take part of some open source project (acegi)
and develop some component that I could use in my thesis. Could you
recommend me something on that?
regards, Vladimir
Vladimir Horev wrote:
Hello list!
I'm planning to write a MSc thesis on the subject of business tier
security. My idea was to take part of some open source project (acegi)
and develop some component that I could use in my thesis. Could you
recommend me something on that?
regards, Vladimir
Hi
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, particular in such a
sensitive (ie commonly-deployed and extended) area as
The new model object filtering is a fascinating area in my mind. One thing
we've implemented (before Acegi had its own filtering) is the ability to
filter down to the property level on an object. In other words, you can
secure a specific property and if someone doesn't have clearance then the
