DokuWiki. Authentication Backends.

Author: Link to original: (English).
Tags: authentication, backend, DokuWiki Submitted by alexgearbox 12.10.2010. Public material.

Translations of this material:

into Russian: «ДокуВики». Бэк-энды аутентификации.. 39% translated in draft.
Submitted for translation by alexgearbox 12.10.2010


====== Authentication Backends ======

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.

===== Backends =====

These are the backends you get with DokuWiki:

* [[auth:ad]] -- Active Directory authentication with optional Single Sign On (SSO)

* [[auth:ldap]] -- authenticate users against a LDAP directory

* [[auth:mysql]] -- access any MySQL database to authenticate users

* [[auth:pgsql]] -- access any Postgres database to authenticate users

* [[auth:plain]] -- the default mechanisms which uses plain text files

===== Contributed Backends =====

These Backends aren't part of the distribution, but might be useful:

* [[|CAS]] -- authenticate with a CAS server

* [[auth:cas]] -- another CAS authentication with ACL based on LDAP attributes

* [[auth:ggauth#chained]] -- chain more than one authentication method

* [[auth:cosign]] -- [[|CoSign]] authentication for Single Sign On (SSO)

* [[auth:django]] -- Authenticates against a Django user database through a Django session cookie.

* [[|Eventum]] -- How to integrate DokuWiki with Eventum Issue Tracker

* [[|drupal]] -- authenticate against a Drupal install

* [[plugin:external]] -- Authentication through an external program -- to be used with PAM & shadow passwords

* [[|gforge]] -- Authenticate against GForge session cookies

* [[auth:ggauth]] -- experimental thoughts on auth backends including chained, split as below plus HTTP basic, htaccess and PAM

* [[tips:htaccessauth#the_htaccess_class|htaccessauth]] -- identify users that already logged in using a Basic HTTP Authorization through .htaccess

* [[auth:imap]] -- authenticate users against an IMAP/POP3 server

* [[|keeyaiwp]] -- SSO with Wordpress

* [[|ldap_local]] -- LDAP authentication with local (plain text) ACLs

* [[auth:lemonldap]] -- authenticate users through a LemonLDAP SSO

* [[auth:mod_auth_tkt]] -- mod_auth_tkt authentication

* [[auth:motp]] -- basically like the plain backend but with added checks for Mobile-OTP tokens

* [[|mybb]] -- authentication using the MyBB forum software

* [[auth:ning]] -- Ning ID authentication

* [[auth:ntlm]] -- NTLM (i.e. Windows NT-based) authentication

* [[auth:pam]] -- Experimental PAM authentication

* [[auth:punbb]] -- authenticate users against the PunBB forum (uses PunBB's cookies and database for SSO)

* [[auth:radius]] -- authenticate users against a RADIUS server

* [[|shibauth]] -- Shibboleth Authentication Backend

* [[auth:ggauth#split]] -- delegate login to one auth backend and groups management to another

* [[auth:smartcard]] -- use a smart card for login

* [[|sympa auth]] -- Authenticate using sympa over SOAP

* [[auth:xmpp]] -- authenticate users against an XMPP/Jabber server

How to implement a new auth backend is described in the [[devel:authentication_backends|HOWTO]].

===== Auth-related plugins =====

* [[plugin:openid]] -- lets register with an OpenID URL; lets already registered users add OpenID URLs to their profiles and then use OpenID to login.

© Андреас Гор и сообщество «ДокуВики». License: CC Attribution-Noncommercial-Share Alike 3.0 Unported