389-ds-base

Clone
Source Code
GIT

#50002 Improve password policy debug logging
Closed: wontfix 3 years ago by spichugi. Opened 5 years ago by mreynolds.

Closed: wontfix
Reopen Issue

Issue Description

Currently there is no way to weasily debug password policy issues. Trying to figure out which local policy rejected the password, or what syntax was actually violated is not possible.

We should:

  1. improve the client message to be more precise (which also ends up in the access log)
  2. Add a new error log level for password policy debugging. Report on things like:
    • Which local policy is rejecting or allowing a password
    • Information on the exact syntax violation

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue set to the milestone: 1.4.1
5 years ago

Metadata Update from @mreynolds:
- Issue priority set to: normal
- Issue set to the milestone: 1.4.4 (was: 1.4.1)
- Issue tagged with: RFE
4 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/3061

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)
3 years ago

Login to comment on this ticket.

Metadata
None

RFE

None
None
normal
None
None
None
Powered by Pagure 5.13.3
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.