Provider specific hooks. The Jaas LoginModule interface doesn't
provide isAccountNonLocked style accessors.
On 3/25/06, Ben Alex [EMAIL PROTECTED] wrote:
Tim Kettering wrote:
Maybe it'd be useful if those checks found in
DaoAuthenticationProvider be made available as a pluggable component
Hey all,
Can someone (Ben?) explain if it is expected to check the various
UserDetails states such as isAccountNonExpired(),
isAccountNonLocked(), isCredentialsNonExpired(), and isEnabled() in a
AuthenticationProvider? This seems to be applied inconsistently...
We had originally been using
Just wanted to put this out here, to see what the developers have to
say about the implications of using a library that uses acegi
internally, inside an application that also uses acegi.
in our case, we're using 1.0 RC, while the library we're evaluating
uses 0.8.2, and that already has brought
to offer more
flexibility. Thanks!
-tim
On 3/2/06, Ben Alex [EMAIL PROTECTED] wrote:
Tim Kettering wrote:
I scoured the forums and mailing list and did not find anyone bringing
up this issue. I suspect it's because everyone (?) so far might have
been using the filter based login. Which we
Hi Everyone.
Mabye there's already a really simple solution that's been staring me
in the face but I'm not seeing it. I'm setting up the remember-me
functionality for this project I'm working on, and due to project
technical considerations, I've have to re-implement parts of the
remember-me in
+1 from me too. I think its better to break stuff now when we still have a
excuse (hey, it ain't 1.0 yet) than post 1.0.
-tim
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Ray Krueger
Sent: Thursday, November 17, 2005 10:01 AM
To:
I ran into a interesting problem when setting up AclVoters for our project.
We are using our own custom AclEntry that subclasses AbstractBasicAclEntry.
So when I tried to set up a class that uses AclVoter, I got a
ClassCastException at this particular section:
for(int i = 0; i entries.length;
the standard used in Acegi.
-tim
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Tim Kettering
Sent: Monday, August 22, 2005 6:42 PM
To: acegisecurity-developer@lists.sourceforge.net
Subject: RE: [Acegisecurity-developer] Blog entry on how to extend
id
parameters
Tim Kettering wrote:
I'm wondering if there was a reason that most of Acegi's standard ACL
classes use int when dealing with object id values. We usually default
to using 'long' instead of 'int' - and I believe that other places do
as well, so it seems to me that it might
] On Behalf Of
Tim Kettering
Sent: Monday, August 22, 2005 10:42 AM
To: acegisecurity-developer@lists.sourceforge.net
Subject: RE: [Acegisecurity-developer] using long for acegi acl id
parameters
Ben,
Yes, sorry I wasn't clear on which class. I meant the AclDetailsHolder in
the JdbcDaoImpl. I've been
I believe it does not work if you extend the class itself, due to how the
internal MappingSqlQuery classes that implement those queries set/reference
themselves. Seems like the default strings get applied via constructor
before the setter methods are called via spring.
I am not 100% on this.
Im wondering if there was a reason that most of Acegis
standard ACL classes use int when dealing with object id values. We usually
default to using long instead of int and I
believe that other places do as well, so it seems to me that it might be
simpler to use long in the acegi
Same here cannot access CVS since
yesterday. I guess SF is messed up again.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Friday, August 19, 2005
11:09 AM
To: acegisecurity-developer@lists.sourceforge.net
Subject:
]
[mailto:[EMAIL PROTECTED] On Behalf Of Tim Kettering
Sent: Friday, July 22, 2005 1:58
PM
To: acegisecurity-developer@lists.sourceforge.net
Subject: [Acegisecurity-developer]
logout functionality
I was looking around for logout tips/practices on the
forums, and I found this thread from a while
I was tracking down some issues that came up after we
started using our own UserDetails object in the principal of Authentication.
This method in JaasNameCallbackHandler seems to be calling the incorrect
method. In AbstractAuthenticationHandler, the methods called are
principal to work with, and that's the user. So if certain
users are going to get extra roles or authorities based on their
username for example writing an AuthorityGranter to do that would be
the way to go.
I hope this helps, or at least made sense.
-Ray
On 7/18/05, Tim Kettering [EMAIL PROTECTED
Hi everyone,
On this project Im working on, we are using JAAS to
authenticate a token, and Acegis JAAS support classes allow for the
translation of the user and its principals to Acegis authority
objects. But in this particular case, we are not interested in the
principals that JAAS
Hi Ben,
Its funny how things like this work out, because I was just pondering a
design issue on friday, and over the weekend, I thought I should
probably email the acegi list about this, and then I read this email
and it seems that you've already provided part, if not the whole
solution.
In
Yes, that would work. Thanks.
-tim
Hi Tim
Yes, the design does require the DAO provider know how to interpret
the presented AclObjectIdentity.
As you know, JdbcDaoImpl (and any BasicAclDao for that matter) needs
to be able to create BasicAclEntry[]s in response to the DAO request.
Each
Hi all,
I was tracking down an issue earlier today regarding running some junit
tests against my code.
Basically I was doing some simple benchmarks on the user authentication
provider, and I decided to throw in the ehcache configuration in the
spring context and thats when it all blew up - the
Nevermind. I just checked CVS and there's already a fix in there, post
0.6 release for this. I'll just go back to the corner where I came
from.
-tim
On Aug 24, 2004, at 3:37 PM, Tim Kettering wrote:
Hi all,
I was tracking down an issue earlier today regarding running some
junit tests against
Thought about posting this in the forum, but thought the dev mailing
list would be a better place to bring this up.
I've gotten my prototype to successfully perform ACL authentication at
the method invocation level. So right now I'm going a bit further
beyond the standard ACL implementation
22 matches
Mail list logo
