You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lécharny (Jira)" <ji...@apache.org> on 2023/04/13 22:19:00 UTC
[jira] [Resolved] (DIRSTUDIO-1307) Error With Password Editor (LDAP Result Code 53)
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lécharny resolved DIRSTUDIO-1307.
------------------------------------------
Fix Version/s: 2.0.0-M18
Resolution: Duplicate
> Error With Password Editor (LDAP Result Code 53)
> ------------------------------------------------
>
> Key: DIRSTUDIO-1307
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1307
> Project: Directory Studio
> Issue Type: Bug
> Affects Versions: 2.0.0-M17
> Reporter: Michael Charles
> Priority: Minor
> Fix For: 2.0.0-M18
>
>
> When I attempted to change a password on my teams test environment using the password editor I got the following error:
> [LDAP result code 53 - unwillingToPerform] Must supply correct old password to change to new one
> In the modification logs I see the following:
> #!RESULT ERROR
> #!CONNECTION *_OUR SERVER_*
> #!DATE _*OUR*_ _*DATE*_
> #!ERROR [LDAP result code 53 - unwillingToPerform] Must supply correct old password to change to new one
> dn: _*OUR*_ _*DN*_
> changetype: modify
> delete: userPassword
> userPassword:: _*OUR HASHED*_ *_PASSWORD VALUE_*
> -
> add: userPassword
> userPassword:: _*OUR HASHED*_ *_PASSWORD VALUE_*
> -
> Looking at older Apache DS Studio builds we had on an older laptop it, it looks like a change was made to the generated LDIF to to perform a delete/add when it originally performed a replace operation instead. I tried creating a replace operation LDIF file and supplied it the created password hash and that still worked on the M17 build, so this appears to be an issue with trying to delete/add instead of replace.
> Our newer laptops are having compatibility issues with the older builds, and while this can be worked around it would be nice to have this working in the newer build. If this change was made to address another issue then perhaps this should be configurable so this can be tweaked to work differently for different server environments.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org