After you have enabled ACL in the config file you need to decide how you like to store user data. DokuWiki supports various methods and creating a new one is pretty easy.
DokuWiki uses so called authentication backends that provide certain methods to store user data and passwords. The user won't even see this backend but you as an administrator have to set up your desired authentication backend and configure it properly.
These are the backends you get with DokuWiki:
ldap – authenticate users against a
LDAP directory
mysql – access any MySQL database to authenticate users
pgsql – access any Postgres database to authenticate users
plain – the default mechanisms which uses plain text files
punbb – authenticate users against the PunBB forum (uses PunBB's cookies and database for SSO)
These Backends aren't part of the distribution, but might be useful:
ad – Active Directory authentication with optional Single Sign On (SSO)
CAS – authenticate with a CAS server
cas – another CAS authentication with
ACL based on
LDAP attributes
-
drupal – authenticate against a Drupal install
htaccessauth – identify users that already logged in using a Basic
HTTP Authorization through .htaccess
radius – authenticate users against a RADIUS server
ntlm – NTLM (i.e. Windows NT-based) authentication
-
pam – Experimental PAM authentication
mybb – authentication using the MyBB forum software
imap – authenticate users against an
IMAP/
POP3 server
xmpp – authenticate users against an XMPP/Jabber server
lemonldap – authenticate users through a LemonLDAP SSO
Eventum – How to integrate DokuWiki with Eventum Issue Tracker
shibauth – Shibboleth Authentication Backend
ggauth – experimental thoughts on auth backends including chained, split as below plus http basic, htaccess and PAM
chained – chain more than one authentication method
split – delegate login to one auth backend and groups management to another
ning – Ning ID authentication
-
How to implement a new auth backend is described in the HOWTO.
