response
parent
ae493178cf
commit
3e6331127b
|
@ -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]]
|
||||
|
|
Loading…
Reference in New Issue