[
https://issues.apache.org/jira/browse/DIRSERVER-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kiran Ayyagari resolved DIRSERVER-1935.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0-M16
Assignee: Kiran Ayyagari
Thank you for the report and the test case, appreciate your time and effort.
Fixed here, http://svn.apache.org/r1551018 .
> Include password policy control in the password modify extended operation
> response if requested
> -----------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1935
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1935
> Project: Directory ApacheDS
> Issue Type: Improvement
> Components: ldap
> Affects Versions: 2.0.0-M16
> Reporter: lucas theisen
> Assignee: Kiran Ayyagari
> Fix For: 2.0.0-M16
>
>
> Adding the password policy control to a PwdModifyRequest results in slightly
> strange behavior. Without the control, if a failure occurs, an exception is
> thrown as expected. With the control, no exception is thrown, but the
> LdapResponse ResultCode is set to INVALID_CREDENTIALS instead of the expected
> CONSTRAINT_VIOLATION, and no controls are included in the response. The
> diagnostic message on the LdapResultDecorator in the response shows that of
> my constraint violation, so I think there are some crossed wires somewhere.
> Workaround: if using a password attribute on an entry (and not a password
> stored outside of the directory), then use a ModifyRequest with just that
> attribute.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
