Lines Matching refs:to
20 real names, email addresses and groups. This is most probably specific to
23 This suggests using authsplit to combine a rather primitive, yet for some reason
27 The example that comes to mind is to use authhttp as PRIMARY auth plugin and
32 plugin combinations as well. Feel free to give me feedback on other working
35 As authsplit has to orchestrate two auth plugins and the user's state in
36 them, it is possible that a user is known to one of the two plugins only or
37 stored with different data. This may lead to the effect that while one auth
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
41 really understand how authsplit works in order to prevent accidental lockout
42 or security breaches due to improper configuration and/or unexpected behavior!
47 In order to understand how authsplit works one doesn't really get around
48 learning about DokuWiki's authentication system. Please refer to
56 here, he is not known to DokuWiki at all.
65 As with checkPass(), _checkUserOnSecondaryAuthPlugin() is then called. Due to
67 additional call to getUserData() to update the global $USERINFO array with the
71 tries to obtain the additional user information (real name, email address,
72 groups) from the SECONDARY auth plugin, which means that the user will have to
81 - otherwise the user seems to DokuWiki to be not logged in and will thus most
82 likely see an "Access denied" page. He or she will either have to register
84 have to create an account for him or her.
86 - logOff(): DokuWiki documentation says this method is run "in addition to the
87 usual logOff. Useful with trustExternal() to initiate actions for the
88 external backend, eg. use it to clear cookies or similar actions".
90 authsplit just delegates the call to the PRIMARY auth plugin's logOff()
93 - getUserData(): this is the method DokuWiki uses eg. to retrieve the user's
96 auth plugin's getUserData() method only to make sure the user exists there and
97 then return the SECONDARY auth plugin's getUserData() information to DokuWiki.
98 Thus, a user has to be known to both auth plugins, but the SECONDARY's user
103 or the Admin uses DokuWiki's user manager to create an account for them.
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
109 to fire up whatever admin tool the PRIMARY auth plugin would otherwise
114 but with an EMPTY password. This is by intent since passwords are supposed to
120 the user self-registration form, users should not be able to specify a
121 password and DokuWiki should not try to generate one for them because it
127 - for login names, real names and email addresses, authsplit will try to
134 - deleteUser(): authsplit will ALWAYS route delete user requests to the
136 accounts known to the PRIMARY auth plugin are yet in use by other software.
141 calls to the SECONDARY auth plugin, following the concept that DokuWiki's
142 user manager is supposed to manage DokuWiki users in the first place. Thus,
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
156 - cleanGroup(): authsplit will always route this method call to the SECONDARY
159 So to summarize which auth plugins are involved in which method calls:
198 would you want to store users in a DokuWiki-specific textfile and put additional
203 try to combine authhttp with authmysql, or authldap with authplain etc. In
211 and rename the extracted directory to "authsplit", otherwise the plugin won't
214 Please refer to http://www.dokuwiki.org/plugins for additional info
215 on how to install plugins in DokuWiki.
221 - primary_authplugin: This is the DokuWiki auth plugin that will be used to
224 - secondary_authplugin: This is the DokuWiki auth plugin that will be used to
228 case-sensitive, it may be necessary to enable this setting to let authsplit
229 convert the username to either uppercase or lowercase (eg. when combining
233 unknown in the SECONDARY auth plugin. If disabled, users will either have to
237 meant to aid in troubleshooting its operation. This setting should not be
240 Note that you'll have to take some of the used auth plugin's settings into
241 consideration whereas some may not apply any longer due to the way authsplit