Farewell, CherryAuth…
…hello, MultiAuth.
As I began to hang out with the CherryPy community more, I understood that using the “Cherry” prefix was somewhat of a mistake as it tied it too closely to the project itself. Of course, no one overtly mentioned that (they are too nice 
), but it just sunk in after a while.
Basically MultiAuth is the same cat in a different skin, for now. In the future, I’d like to provide for two basic authentication “front-ends”; forms based (what it uses now) and browser based (using some of Sylvain’s work, most likely).
If you look at the source code of MultiAuth, you’ll see that it is pretty hackish. Metaclasses, decorators and the like. I’d like to rewrite MultiAuth in the “CP way” (as a filter), but I also like to define the security settings in the code. Since filters operate at the HTTP request/response level, it seems like it would be hard to get at the method attributes that I use to specify required security clearance.
So it is what it is for now.
cw