Differences

This shows you the differences between two versions of the page.

--- rfc:ldap_exop [2017/06/29 14:33] – mcmic
+++ rfc:ldap_exop [2017/07/04 07:52] – mcmic
@@ Line 31: / Line 31: @@
 This RFC also wish to introduce helper functions for common EXOP usage:
 <code php>
-bool ldap_exop_whoami(resource $link, string &$result)
+bool|string ldap_exop_whoami(resource $link)
-bool ldap_exop_passwd(resource $link, string $user, string $oldpw, string $newpw [, string &$genpw])
+bool|string ldap_exop_passwd(resource $link, [string $user, [string $oldpw, [string $newpw]]])
 </code>
-The first one would call whoami EXOP and fill $result with the result. Return TRUE or FALSE upon failure.
+The first one would call whoami EXOP and returns the result. Returns FALSE upon failure.
-The second one would call passwd EXOP and return TRUE or FALSE upon failure. If $newpw is empty, $genpw will be filled with the generated password for the user. If $user is empty, it affects the bound user.
+The second one would call passwd EXOP and return TRUE or FALSE upon failure. If $newpw is empty, returns the generated password for the user. If $user is empty, it affects the bound user.
 The author of the original patch stated that technically ldap_start_tls is an exop helper and therefore could be renamed ldap_exop_start_tls. We feel this would be a useless BC.