> would it make sense to do away > entirely with this caching code, and leave management of credentials to > the upstream authnz providers?
I remember this particular caching layer causing a one or two insidious bugs in the past, all of which were nearly impossible to figure out. I would be wary of doing anything other than (a) keeping the classic (non-fesl) authN code in its present state, caching and all or (b) deprecating with the intent of full removal. > On a related note: are these three filters still relevant/useful, or > have they been supplanted by FeSL (at least FilterXmlUserFile and > FilterLdap)? Would it make sense to deprecate these filters in a future > release? That's a good question. I don't think any of the system tests exercise the classic authn code any more, and I think deprecation/removal was an ultimate target. -Aaron ------------------------------------------------------------------------------ Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev _______________________________________________ Fedora-commons-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
