response

diff --git a/doc/bugs/anonok_vs._httpauth.mdwn b/doc/bugs/anonok_vs._httpauth.mdwn
index d63e365c11bcc513bf7562c0f464e01702b2f358..688274d679e4c610fe7e83186d8c43bd48c5c47a 100644 (file)
--- a/doc/bugs/anonok_vs._httpauth.mdwn
+++ b/doc/bugs/anonok_vs._httpauth.mdwn
@@ -16,3 +16,11 @@ and a whitelist of OpenIDs in `locked_pages`...)
 > to bounce through the cgiauthurl and actually sign in. This would be
 > significantly different than the regular httpauth process, in which the
 > user signs in in passing. --[[Joey]]
+
+>> My primary userbase has grown accustomed to the seamlessness of
+>> httpauth with SPNEGO, so I'd rather not reintroduce a seam into
+>> their web-editing experience in order to let relatively few outsiders
+>> edit relatively few pages. When is the decision made about whether
+>> the current page can be edited by the current user (if any)? What
+>> if there were a way to require particular auth plugins for particular
+>> PageSpecs? --[[schmonz]]