#3396 RFE: remove allow_missing_name PAM option
Closed: wontfix by pbrezina. Opened by abbra.

Let SSSD to decide whether missing name in PAM conversation of certificate-based authentication is allowed or not based on the certificate mapping properties, not upfront from pam_sss configuration.

I believe current setup is hurting admin experience due to the need to set allow_missing_name option on all machines where and when there is a need to allow role-based logon. SSSD should already know that missing name in PAM exchange is OK for smartcard-based logon if certificate mapping allows that. PAM module (pam_sss) config should not be involved.

Sumit's point is that PAM config modification is needed anyway to enable pam_sss and disable pam_pkcs11 so setting option is "OK". However, the option itself is not required because logic-wise (not code-wise, this is what this RFE is about to change) SSSD can discover whether allow_missing_name behavior is required or not once it finds out that pam_sss performs smartcard authentication. So option itself becomes redundant, only to avoid contacting SSSD. However, if such option is always specified in pam_sss config, why can't be its behavior be default at all?


Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD Future releases (no date set yet)

Metadata Update from @thalman:
- Issue tagged with: Canditate to close

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/4423

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