SSSD / sssd

#2600 Predefined user message if chpass_provider = none
Closed: wontfix by pbrezina. Opened by diablo80.

Closed: wontfix
Reopen Issue

An option like pam_password_prohibit_message would be beneficial for pam_sss module. If the chpasswd_provider is set to none an error message is displayed "passwd: Authentication token manipulation error" using passwd command.

A note to the (ldap) user should be shown that for password change another mechanism has to be used.

The "none" provider handling is currently suboptimal, we should treat it as a built-in provider, just like "simple". Currently I only see errors if auth_provider=none is used:

(Mon Mar 16 09:58:08 2015) [sssd[be[ipa.example.com]]] [be_pam_handler] (0x0100): Got request with the following data
(Mon Mar 16 09:58:08 2015) [sssd[be[ipa.example.com]]] [pam_print_data] (0x0100): command: PAM_AUTHENTICATE
(Mon Mar 16 09:58:08 2015) [sssd[be[ipa.example.com]]] [pam_print_data] (0x0100): domain: ipa.example.com
(Mon Mar 16 09:58:08 2015) [sssd[be[ipa.example.com]]] [pam_print_data] (0x0100): user: admin
(Mon Mar 16 09:58:08 2015) [sssd[be[ipa.example.com]]] [pam_print_data] (0x0100): service: su-l
(Mon Mar 16 09:58:08 2015) [sssd[be[ipa.example.com]]] [pam_print_data] (0x0100): tty: pts/1
(Mon Mar 16 09:58:08 2015) [sssd[be[ipa.example.com]]] [pam_print_data] (0x0100): ruser: jhrozek
(Mon Mar 16 09:58:08 2015) [sssd[be[ipa.example.com]]] [pam_print_data] (0x0100): rhost: 
(Mon Mar 16 09:58:08 2015) [sssd[be[ipa.example.com]]] [pam_print_data] (0x0100): authtok type: 1
(Mon Mar 16 09:58:08 2015) [sssd[be[ipa.example.com]]] [pam_print_data] (0x0100): newauthtok type: 0
(Mon Mar 16 09:58:08 2015) [sssd[be[ipa.example.com]]] [pam_print_data] (0x0100): priv: 0
(Mon Mar 16 09:58:08 2015) [sssd[be[ipa.example.com]]] [pam_print_data] (0x0100): cli_pid: 1331
(Mon Mar 16 09:58:08 2015) [sssd[be[ipa.example.com]]] [pam_print_data] (0x0100): logon name: not set
(Mon Mar 16 09:58:08 2015) [sssd[be[ipa.example.com]]] [be_pam_handler] (0x1000): Undefined backend target.
(Mon Mar 16 09:58:08 2015) [sssd[be[ipa.example.com]]] [be_pam_handler] (0x0100): Sending result [28][ipa.example.com]
(Mon Mar 16 09:58:08 2015) [sssd[pam]] [sbus_remove_timeout] (0x2000): 0xb33b80
(Mon Mar 16 09:58:08 2015) [sssd[pam]] [sbus_dispatch] (0x4000): dbus conn: 0xb2fb90
(Mon Mar 16 09:58:08 2015) [sssd[pam]] [sbus_dispatch] (0x4000): Dispatching.
(Mon Mar 16 09:58:08 2015) [sssd[pam]] [pam_dp_process_reply] (0x0200): received: [28 (Module is unknown)][ipa.example.com]

But I don't quite agree with the ticket being 'critical'. I suspect this ticket won't make 1.13 unless patches are provided externally, although I agree with the intent of this ticket.

priority: critical => minor

Fields changed

milestone: NEEDS_TRIAGE => SSSD Deferred

Fields changed

rhbz: => todo

Metadata Update from @diablo80:
- Issue set to the milestone: SSSD Patches welcome

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

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

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/3641

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
None
None
None
None
High
enhancement
SSSD
1.11.2
0
0
todo
0
0
0
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.