Edit report at https://bugs.php.net/bug.php?id=47222&edit=1
ID: 47222
Comment by: daniellucenag at gmail dot com
Reported by: webe4703 at uni-trier dot de
Summary: Ldap error messages are very unprecise
Status: Open
Type: Feature/Change Request
Package: LDAP related
Operating System: Linux (Ubuntu)
PHP Version: 5.2.8
Block user comment: N
Private report: N
New Comment:
I need to change a password of a user in AD, but the error code is very much generic! this request
is perfect for my problem! please solve this!
Previous Comments:
------------------------------------------------------------------------
[2015-03-02 14:12:22] johnnywiller10 at gmail dot com
Anyone has an workaround to this?
------------------------------------------------------------------------
[2015-03-02 14:12:21] johnnywiller10 at gmail dot com
Anyone has an workaround to this?
------------------------------------------------------------------------
[2015-03-02 14:12:19] johnnywiller10 at gmail dot com
Anyone has an workaround to this?
------------------------------------------------------------------------
[2013-04-11 13:08:58] carmageddon at gmail dot com
I found a partial implementation of this feature in Python, inspecting the
Python's source for this might shorten the time to bring this feature to PHP:
http://mail.python.org/pipermail/python-ldap/2012q2/003129.html
Hope that helps, we really need this!
Thanks
------------------------------------------------------------------------
[2011-05-24 18:45:49] post at rolandgruber dot de
Hi,
it would be great if this could be fixed. It is impossible to give e.g. precise error messages to
users if PHP only returns a generic error message.
One more example:
User wants to change password but ppolicy blocks the change because of password reuse.
The LDAP server sends 19: constraint violation (Password is in history of old passwords)
PHP returns: 19: constraint violation
This makes it impossible to provide a useful error message to a user. :(
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=47222
--
Edit this bug report at https://bugs.php.net/bug.php?id=47222&edit=1