Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2049640

Summary:	sssd does not convey LDAP password policy state to end users
Product:	Red Hat Enterprise Linux 8	Reporter:	Anton Bobrov <abobrov>
Component:	sssd	Assignee:	sssd-maint
Status:	CLOSED WONTFIX	QA Contact:	sssd-qe
Severity:	low	Docs Contact:
Priority:	low
Version:	8.3	CC:	aboscatt, grajaiya, jhrozek, lslebodn, mzidek, pbrezina, pkettman, tscherf
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-31 17:12:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Anton Bobrov 2022-02-02 13:50:10 UTC

Description of problem:

When sssd is configured with LDAP access provider and the LDAP server has password policies in place which put constraints on certain operations eg password quality checks sssd does not propagate related LDAP password policy errors (constraints violations) to end user tools such as 'passwd'. sssd error logs show actual password policy constraints as responses from LDAP backend eg

(2022-01-21 16:19:43): [be[example.com]] [sdap_exop_modify_passwd_done] (0x1000): [RID#369] Password Policy Response: expire [-1] grace [-1] error [Password fails quality checks].
(2022-01-21 16:19:43): [be[example.com]] [sdap_exop_modify_passwd_done] (0x0080): [RID#369] ldap_extended_operation result: Constraint violation(19), Failed to update password

but they are not propagated.

Actual results:

Password change failed. Server message: Failed to update password

Expected results:

Password change failed. Server message: Password fails quality checks

Comment 1 Andre Boscatto 2023-05-31 17:12:59 UTC

Please know that we carefully considered and evaluated your request and its potential impact on our product roadmap, market demand, and overall strategy.

While we understand that addressing enhancements, bugs, and issues is critical for ensuring the quality and reliability of our product, we need to balance these priorities with our long-term goals and resource constraints. Unfortunately, we cannot address this request at this time as it does not align with our product vision and strategy, and keeping it in the backlog would be misleading and give the false impression that we will address it in the future, thus we are closing it.

Although we cannot address this specific request, we encourage anyone to collaborate and contribute to the upstream communities, as this approach enhances the flexibility, scalability, and customization of our solution while maintaining its security and stability.

We apologize for any inconvenience this may cause, and we understand that it can be frustrating when requests/expectations are not met. However, we hope that you can appreciate that we must balance our priorities with our long-term goals and resource constraints.

Please be aware that while you are welcome to open a new support case or reopen this request, we cannot guarantee that it will be addressed due to resource constraints and the prioritization of other requests.

Once again, thank you for taking the time to share feedback with us, and we look forward to continuing to work together to deliver the best possible solution, supporting in any way we can.

Thank you for understanding,

André Boscatto
Product Owner - Identity and Access Management Department