Hi everyone
Today I upgraded Acegi Security CVS to Spring 1.1 RC 1 JARs and the
integration tests system has shown no incompatibilities.
It's almost time to release version 0.6:
- Unit tests and container integration tests pass
- The upgrade-05-06.txt file is complete
- Unit test coverage is
[EMAIL PROTECTED] wrote:
Ben,
*Still having trouble submitting to the forum / keeps bouncing back...*
Thanks for your reply. First, you were right about my HibernateDAO. It
was not using the same credentials as the in-memory representation. In
fact the user that I was pulling back did not have
+1 (I was waiting for the Websphere patch to the Authentication filter
from the HEAD :)
Good job Ben.
|-+---
| | Ben Alex [EMAIL PROTECTED]|
| | Sent by:|
|
Unfortunately I've been pretty swamped at work as of late, and haven't had the opprotunity to put together any external documenation on the Jaas provider.
The classes are pretty heavily javadoc'd, and are not that complex at all really. The only real complexity is Jaas itself, more so than
Andy Depue wrote:
I've implemented security in my web application using Acegi security. I'm in
the process now of implementing a very simple password policy (basically, the
administrator has the ability to set a flag on the user to force them to
change their password the next time they log
March, Andres wrote:
I am still wondering about the usage of the acl stuff. I see in your
test how the GrantedAuthorityEffectiveAclsResolver can be used directly
but would it be worthwhile to provide a voter that can perform acl
authorization?
I will be writing one in about 3 weeks but I am sure
