map of authentication methods for cyrus

[Craig Ringer]

>Ken Murchison wrote:
>>Craig, this is a good start, but as Rob said, you've left out the
>>mechanism layer.

Hmm... thanks. It appears that there's something lacking in my 
understanding of the authentication scheme, but the posts on this thread 
have given me some idea where to look and learn. I'll include that shortly.

It's a little tricky trying to do any kind of documentation on a project 
that I don't know inside out, but it's clearly needed and I'm game to 
try. I'll try to avoid too many stupid errors or questions. Still, if 
nobody minds I think it best to scratch out an outline and some content 
then refine it once it's mostly there - if I try to get it perfect 
first, it'll never get anywhere.

Thanks for the initial comments, they're much appreciated.

Rob Siemborski wrote:
> I'd also be much more inclined to accept this into the distribution if it
> was in an easily modifiable format (at this point, I suspect that means
> xfig, but if you have another suggestion I'm willing to listen).

The current format is OO.o draw. PostScript & PDF formats are easy from 
there, of course. If another format is needed I'm sure I can manage - 
within reason - but I'd like to get the content right first. What I was 
thinking of as the goal for this was to use it as part of a FAQ on cyrus 
authentication. Sections on mailbox recovery, backup/restore, etc could 
be added later. I've been jotting bits from mailing list discussion for 
this purpose for a little while now.

Craig Ringer