Lines Matching full:be

19      * Possible things an auth backend module may be able to
20      * do. The things a backend can do need to be set to true
24         'addUser' => false, // can Users be created?
25         'delUser' => false, // can Users be deleted?
26         'modLogin' => false, // can login names be changed?
27         'modPass' => false, // can passwords be changed?
28         'modName' => false, // can real names be changed?
29         'modMail' => false, // can emails be changed?
30         'modGroups' => false, // can groups be changed?
31         'getUsers' => false, // can a (filtered) list of users be retrieved?
32         'getUserCount' => false, // can the number of users be retrieved?
33         'getGroups' => false, // can a list of available groups be retrieved?
89                 // can at least one of the user's properties be changed?
94                 // can at least anything be changed?
150      * only be needed when trustExternal is implemented.
164      * If this function is implemented it will be used to
166      * will not be used for authenticating (except this
172      * The function can be used to authenticate against third
176      * The function will be called with or without a set
179      * need to be checked. If no username was given it
219      * Check user+password [ MUST BE OVERRIDDEN ]
224      * May be ommited if trustExternal is used.
238      * Return user info [ MUST BE OVERRIDDEN ]
264      * The new user HAS TO be added to the default group by this
289      * @param   string $user nick of the user to be changed
290 …   * @param   array $changes array of field/value pairs to be changed (password will be clear text)
316      * [should be implemented whenever retrieveUsers is implemented]
336      * @param   int $start index of first user to be returned
337      * @param   int $limit max number of users to be returned, 0 for unlimited
395      * the backend and should also be applied to any user name within
398      * This should be used to enforce username restrictions.
413      * the backend and should also be applied to any groupname within
416      * This should be used to enforce groupname restrictions.
418      * Groupnames are to be passed without a leading '@' here.
436      * This also means that changes to the user database will not be reflected