-
Notifications
You must be signed in to change notification settings - Fork 451
How can I obtain detailed information about the password policy? #946
Comments
It sounds like you are asking about support for the controls described in https://datatracker.ietf.org/doc/html/draft-behera-ldap-password-policy-10#anchor52 (§6,6.1,6.2). That doc is a draft doc and I cannot find an accepted "RFC" version of it. However, servers, including OpenLDAP, have implemented the proposed spec regardless of the draft status. Thus, we are not opposed to it being added here. The controls we currently support are plainly listed at https://github.com/ldapjs/controls/tree/9718b85dc8eae4522e5d879a603a13422d6e245a/lib/controls. The controls in question are not in that list. If you would like support for them, you are welcome to work on the feature. At a minimum, such work is likely to require:
Would you like to work on this? |
For example, when I enter the following command as a shell command, the rejection reason is displayed through the Additional Info message:
However, when I use ldapjs to call the modify operation for the userPassword value, only the following error is generated: would like to obtain additional information like "Password is too young to change." Is it currently not supported by ldapjs? |
Did you read my previous reply? |
@jsumners
Based on your previous answer, it looks like the second case is correct. |
The requested feature is not implemented. I outlined the minimum of what would need to be done to implement the feature. |
I understand. :) |
No. You are welcome to work on it. |
Try and if it works well, I'll share it. |
Being worked on in #949. |
Solved by #949. |
It appears that we can obtain detailed information regarding password policy in version 3 through the following issues:
#186
#770
#839 (version 3 clean slate notification)
However, i was unable to obtain any detailed information during the bind process.
Could you please provide a sample code if possible?
The text was updated successfully, but these errors were encountered: