rfc:ldap_exop
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
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: | This RFC also wish to introduce helper functions for common EXOP usage: | ||
<code php> | <code php> | ||
- | bool ldap_exop_whoami(resource $link, string & | + | bool|string |
- | bool ldap_exop_passwd(resource $link, string $user, string $oldpw, string $newpw | + | bool|string |
</ | </ | ||
- | The first one would call whoami EXOP and fill $result with the result. | + | The first one would call whoami EXOP and returns |
- | The second one would call passwd EXOP and return TRUE or FALSE upon failure. If $newpw is empty, | + | The second one would call passwd EXOP and return TRUE or FALSE upon failure. If $newpw is empty, |
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. | 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. |
rfc/ldap_exop.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1