mån 2010-08-16 klockan 21:32 +1200 skrev Amos Jeffries:
> I don't think thats making them scheme-specific as such. The child
> classes inheriting from AuthUser will be doing that part.
It does. Each instance of AuthUser is scheme specific, and because of
this the related acls break down when more than once scheme is
configured.
> Config can be unlinked by moving the TTL into AuthUser as a generic
> timestamp set at point of last validation. IIRC thats all its used for
> so the validating scheme's TTL-when-validated can persist across
> reconfigure.
What validation?
AuthUser is (or should be) Squids general view of a user/login. Not for
tracking scheme details.
> auth_type is just a meta data flag. Useful for cachemgr display and any
> scheme-specific logics handling the AuthUser that fell like they need to
> check the type.
Then they are abusing AuthUser.
Regards
Henrik
Received on Mon Aug 16 2010 - 13:32:48 MDT
This archive was generated by hypermail 2.2.0 : Mon Aug 16 2010 - 12:00:05 MDT