On Mon, Jun 16, 2008 at 07:29:12PM +0200, Pierangelo Masarati wrote:

Not sure what you mean there, but I believe the fact that the implementation is in saslauth.c is for mere historical reasons. Right now, authorization code is independent from SASL, and is used by a number of features: SASL authz, RFC 4370, identity assertion, dgIdentity and more.

I was referring to documentation, where the only bit of the admin guide that really talks about proxy authorisation is the SASL section.

Andrew