make getUserData() fail safely on non-string input

When removing multiple users at once, plugins listening on the
AUTH_USER_CHANGE event may pass the array of user names (params[0]
for 'delete') to

make getUserData() fail safely on non-string input

When removing multiple users at once, plugins listening on the
AUTH_USER_CHANGE event may pass the array of user names (params[0]
for 'delete') to getUserData(), which crashed authplain with an
"Array to string conversion" / illegal offset error.

Guard the bundled auth backends so a non-string user fails safely
by returning false, and document that AUTH_USER_CHANGE params[0] is
a string for create/modify but a string[] for delete.

Fixes #4567

show more ...

Translation update (sk)

Translation update (tr)

Translation update (ca)

Translation update (pt-br)

Translation update (it)

translation update

translation update

translation update

fix: #3796 LDAP mail can be null

translation update

translation update

translation update

translation update

translation update

authldap: avoid warning on invalid mapping setup. #4399

translation update

translation update

translation update

translation update

�� Rector and PHPCS fixes

Add option 'modPassPlain' to send plaintext password updates to LDAP server

translation update

Support a URI parameter for ldap since current code doesn't actually work

translation update