Lines Matching refs:is

16   passwords only. This is where authentication really happens and the
17   authentication source behind this plugin is most probably shared with other
20   real names, email addresses and groups. This is most probably specific to
24 particularly useful auth plugin with an auth plugin that is more powerful, yet
27 The example that comes to mind is to use authhttp as PRIMARY auth plugin and
30 HTTP authentication can't offer, such as email addresses. This is the scenario
36 them, it is possible that a user is known to one of the two plugins only or
38 plugin knows about him or her, (s)he is still being reported to DokuWiki as
40 sight, you should read the following explanations carefully. It is ESSENTIAL to
53 - checkPass(): this is DokuWiki's method that validates login names and
55   validates both login name and password successfully. If a user is not known
56   here, he is not known to DokuWiki at all.
61 - trustExternal(): this is the method DokuWiki calls if the PRIMARY auth
63   do whatever authentication is required, eg. against a third-party cookie.
65   As with checkPass(), _checkUserOnSecondaryAuthPlugin() is then called. Due to
70 - _checkUserOnSecondaryAuthPlugin(): This is an internal helper method that
86 - logOff(): DokuWiki documentation says this method is run "in addition to the
93 - getUserData(): this is the method DokuWiki uses eg. to retrieve the user's
102 - createUser(): this is the method that gets called if users register themselves
105   authsplit will first check if the user is not known to the PRIMARY auth plugin
106   yet and whether it is capable of adding users. If so, it will try to create
107   the user there, first. This is so that you can use DokuWiki to quickly create
112   If successful (or the PRIMARY auth plugin does not support adding users, as is
113   the case for authhttp), the user is then created in the SECONDARY auth plugin
114   but with an EMPTY password. This is by intent since passwords are supposed to
119   too. If not (and this is the case eg. for authhttp), this also means that in
129     capable of modifying it, that is), then in the SECONDARY auth plugin.
135   SECONDARY auth plugin only. This is because it can't know whether user
142   user manager is supposed to manage DokuWiki users in the first place. Thus,
145   is enabled, only the SECONDARY auth plugin would really know which users resp.
149   to the SECONDARY auth plugin since, by design, that is where group membership
153   calls to the PRIMARY auth plugin since that is the one that dictates
157   auth plugin since that is the one that dictates restrictions on group names.
197 Of course, this example is not a particular useful combination. After all, why
202 as the SECONDARY auth plugin is the prime use case. You could of course also
221 - primary_authplugin: This is the DokuWiki auth plugin that will be used to
222   validate login names and passwords. An example candidate is my authhttp
224 - secondary_authplugin: This is the DokuWiki auth plugin that will be used to
227 - username_caseconversion: If one of the two auth plugins used is
230   authldap which is case-insensitive with authsplit which is not).
260 This plugin is based on ideas in the "ggauth" auth backend by Grant Gardner
263 concept is unlikely.