Item13386: {LoginManager} = 'none' applies ACL checks, locks user out of configure, and faults if bin/login accessed.

How to reproduce

1. Bootstrap
   • create an fresh installation of the foswiki
   • bootstrap it (i'm using tools/lighhtpd.pl for the testing)
   • set the internal admin password
   • save
   • check the working wiki
   • quit the browser
2. Reconfig
   • in the configure -> Security -> Login
   • set the {LoginManager} to none
   • save
3. try the result
   • can't create any topic, nor edit any (the CHANGE access is missing for the WikiGuest
   • can't access the configure to restore back
   • completely locked out - need manually from the shell restore the !LocalSite.cfg
4. the needs
   • warn the user about the ACL for the WikiGuest, because he can't edit any his old topic
   • somewhat allow to access the configure

-- JozefMojzis - 26 Apr 2015

The setting of "none" is documented as allowing full access with no restrictions.

• none - Don't support logging in, all users have access to everything.

1. Foswiki::Configure::Auth should just return and not throw any errors if LoginManager is set to 'none'.
2. Foswiki::Access::TopicACLAccess should allow all access when LoginManager is set to 'none'

TopicACLReadOnlyAccess should probably still enforce read-only.

Note there is another related error: bin/login script throws an error:

Foswiki detected an internal error - please check your Foswiki logs and webserver logs for more information.

Can't locate object method "login" via package "Foswiki::LoginManager"

-- GeorgeClark - 26 Apr 2015

Commenting is disabled while not logged in