https://bugzilla.redhat.com/show_bug.cgi?id=1334254 (In reply to Marc Sauton from comment #4)
added a public comment 34 to the salesforce case number 01617092 about not removing the first and last name / givenname and sn from the hardcoded list in check_pw_syntax_ext() In fact, I would rather add some attributes from the objectclass posixaccount, inetorgperson, and person than remove some. Also asked for suggestions on how to eventually improve that hardcoded list (is it worth/does it make sense to make it a custom list of "valid" attributes?)
Metadata Update from @firstyear: - Issue set to the milestone: 1.3.6 backlog
Metadata Update from @firstyear: - Custom field component reset (from Security - Password Policy) - Issue close_status updated to: None - Issue set to the milestone: 1.4 backlog (was: 1.3.6 backlog)
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field reviewstatus adjusted to None - Custom field version adjusted to None - Issue tagged with: RFE
This was added to 1.4.0
Metadata Update from @mreynolds: - Issue assigned to mreynolds - Issue set to the milestone: 1.4.0 (was: 1.4 backlog)
Metadata Update from @mreynolds: - Assignee reset - Issue close_status updated to: fixed - Issue set to the milestone: 1.4 backlog (was: 1.4.0) - Issue status updated to: Closed (was: Open)
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/1927
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)