piravate_wiki plugin isn't clear enough

[ghost]

When the plugin pirvate_wiki is enabled, the sign up tab is shown but is impossible to sign up.
While this should be one of the following behaviors:

• the sign up tab isn't shown and it's impossible to sign up
• the sign up tab is shown and it's possible to sign up

[minad]

You are right about that. But there is the configuration authentication.enable_signup which you can use to prevent this.

I keep this open for now. I might rewrite some parts of the authentication system in the future because it is not flexible enough (Single-sign on, OpenID, things like that).

[RolandHoGH]

What is needed to enable sign up with private_wiki ? Any hints to do that quickly would be appreciated.

[RolandHoGH]

This seemed to help:

diff --git a/plugins/security/private_wiki.rb b/plugins/security/private_wiki.rb
index cd6a95d..8966a87 100644
--- a/plugins/security/private_wiki.rb
+++ b/plugins/security/private_wiki.rb
@@ -2,7 +2,7 @@
description 'Forbid anonymous access, redirect to login'

class ::Olelo::Application

• PUBLIC_ACCESS = %w(/login)
• PUBLIC_ACCESS = %w(/login /signup)

redefine_method :include_page do |path|
User.logged_in? ? super(path) : ''

[minad]

Well in this case anyone can access the wiki (by signing up). Olelo has plugabble auth backends. So in principle you could connect it to something else (LDAP, etc)

[RolandHoGH]

Am Freitag, 31. Mai 2013, 00:54:42 schrieb Daniel Mendler:

Well in this case anyone can access the wiki (by signing up).
Olelo has plugabble auth backends. So in principle you could connect it to something else (LDAP, etc)

Yeah, I noticed that. I need it only for a defined small group of 7 people. Perhaps an acl on /signup would help
and then creating all accounts as admin?

LDAP seems to be an overkill for my needs.

Roland Hautz www.hautz.de/Roland_Hautz_OpenPGP.asc :
925B CB98 7A4F 25E0 E128 A309 97C3 2FA0 288F FFA6
Macht ist geil. Humor ist Pflicht. Skepsis ist eine Tugend!

[minad]

Currently you can only define acls on pages.

[minad]

In your case you could just create the user yaml file statically.

[RolandHoGH]

On a slightly different topic: I deployed it to heroku and since there one can see only stdout/stderr output,
a way of directing Logger output to STDOUT is needed. I already tried a few log: file: settings in config.yml
to no avail. How could I change this?

Am Freitag, 31. Mai 2013, 00:54:42 schrieb Daniel Mendler:

Well in this case anyone can access the wiki (by signing up). Olelo has plugabble auth backends. So in principle you could connect it to something else (LDAP, etc)

Roland Hautz www.hautz.de/Roland_Hautz_OpenPGP.asc :
925B CB98 7A4F 25E0 E128 A309 97C3 2FA0 288F FFA6
Macht ist geil. Humor ist Pflicht. Skepsis ist eine Tugend!

[RolandHoGH]

Am Freitag, 31. Mai 2013, 01:08:16 schrieb Daniel Mendler:

In your case you could just create the user yaml file statically.
Right. It's a little bit ugly, because I have to check that file into git in order to
get it deployed to heroke, but it should work. You'll get no pull request, though ;-)

Roland Hautz www.hautz.de/Roland_Hautz_OpenPGP.asc :
925B CB98 7A4F 25E0 E128 A309 97C3 2FA0 288F FFA6
Macht ist geil. Humor ist Pflicht. Skepsis ist eine Tugend!