Feature changed by: Jiri Srain (jsrain) Feature #313142, revision 5 Title: YaST support only SSSD for LDAP based authentication openSUSE Distribution: Unconfirmed Priority Requester: Mandatory Requested by: Ralf Haferkamp (rhafer) Partner organization: openSUSE.org Description: We should remove support for nss_ldap and pam_ldap configuration from the YaST ldap-client module (note: this is not a request to remove nss_ldap and pam_ldap from the distribution) and only support SSSD for LDAP based users authentication. The nss_ldap and pam_ldap packages should still be part of future distribution to still allow manual setup. When updating an nss-/pam_ldap based system from an older release it should stay with nss-/pam_ldap. Upon first startup of yast2-ldap-client it might offer a migration to sssd. Business case (Partner benefit): openSUSE.org: Focussing on a single implementation for LDAP authentication allows us to provide a cleaner UI and should reduce the complexity of the YaST ldap-client module considerably. Making it easier to use and maintain. + Discussion: + #1: Jiri Srain (jsrain) (2012-01-19 10:03:14) + Joe, Matthias, this is in fact about removing existing functionality. + How comon are the non-SSSD set-ups? -- openSUSE Feature: https://features.opensuse.org/313142

Feature changed by: Andreas Jaeger (a_jaeger) Feature #313142, revision 13 Title: YaST support only SSSD for LDAP based authentication - openSUSE Distribution: Unconfirmed + openSUSE Distribution: Evaluation by project manager Priority Requester: Mandatory Requested by: Ralf Haferkamp (rhafer) Partner organization: openSUSE.org Description: We should remove support for nss_ldap and pam_ldap configuration from the YaST ldap-client module (note: this is not a request to remove nss_ldap and pam_ldap from the distribution) and only support SSSD for LDAP based users authentication. The nss_ldap and pam_ldap packages should still be part of future distribution to still allow manual setup. When updating an nss-/pam_ldap based system from an older release it should stay with nss-/pam_ldap. Upon first startup of yast2-ldap-client it might offer a migration to sssd. Business case (Partner benefit): openSUSE.org: Focussing on a single implementation for LDAP authentication allows us to provide a cleaner UI and should reduce the complexity of the YaST ldap-client module considerably. Making it easier to use and maintain. Discussion: #1: Jiri Srain (jsrain) (2012-01-19 10:03:14) Joe, Matthias, this is in fact about removing existing functionality. How comon are the non-SSSD set-ups? #6: Jan Engelhardt (jengelh) (2012-01-23 22:36:15) (reply to #1) They can be migrated. -- openSUSE Feature: https://features.opensuse.org/313142

Feature changed by: Jiri Srain (jsrain) Feature #313142, revision 17 Title: YaST support only SSSD for LDAP based authentication - openSUSE Distribution: Evaluation by project manager + openSUSE Distribution: Evaluation by engineering manager Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Ralf Haferkamp (rhafer) Partner organization: openSUSE.org Description: We should remove support for nss_ldap and pam_ldap configuration from the YaST ldap-client module (note: this is not a request to remove nss_ldap and pam_ldap from the distribution) and only support SSSD for LDAP based users authentication. The nss_ldap and pam_ldap packages should still be part of future distribution to still allow manual setup. When updating an nss-/pam_ldap based system from an older release it should stay with nss-/pam_ldap. Upon first startup of yast2-ldap-client it might offer a migration to sssd. Business case (Partner benefit): openSUSE.org: Focussing on a single implementation for LDAP authentication allows us to provide a cleaner UI and should reduce the complexity of the YaST ldap-client module considerably. Making it easier to use and maintain. Discussion: #1: Jiri Srain (jsrain) (2012-01-19 10:03:14) Joe, Matthias, this is in fact about removing existing functionality. How comon are the non-SSSD set-ups? #6: Jan Engelhardt (jengelh) (2012-01-23 22:36:15) (reply to #1) They can be migrated. -- openSUSE Feature: https://features.opensuse.org/313142

Feature changed by: Jiří Suchomel (jsuchome) Feature #313142, revision 19 Title: YaST support only SSSD for LDAP based authentication openSUSE Distribution: Ready Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Ralf Haferkamp (rhafer) Partner organization: openSUSE.org Description: We should remove support for nss_ldap and pam_ldap configuration from the YaST ldap-client module (note: this is not a request to remove nss_ldap and pam_ldap from the distribution) and only support SSSD for LDAP based users authentication. The nss_ldap and pam_ldap packages should still be part of future distribution to still allow manual setup. When updating an nss-/pam_ldap based system from an older release it should stay with nss-/pam_ldap. Upon first startup of yast2-ldap-client it might offer a migration to sssd. Business case (Partner benefit): openSUSE.org: Focussing on a single implementation for LDAP authentication allows us to provide a cleaner UI and should reduce the complexity of the YaST ldap-client module considerably. Making it easier to use and maintain. Discussion: #1: Jiri Srain (jsrain) (2012-01-19 10:03:14) Joe, Matthias, this is in fact about removing existing functionality. How comon are the non-SSSD set-ups? #6: Jan Engelhardt (jengelh) (2012-01-23 22:36:15) (reply to #1) They can be migrated. #8: Lukas Ocilka (locilka) (2013-09-02 17:02:29) Jiri, please, go ahead and implement this feature. + #9: Jiří Suchomel (jsuchome) (2013-09-03 15:54:41) + Well, current yast2-ldap-client offers UI only for SSSD. If nss is + detected, it will be rewritten to SSSD on exit. + So I think this is what was requested. Ralf, could you confirm? Than we + could close the feature. -- openSUSE Feature: https://features.opensuse.org/313142

Feature changed by: Jiří Suchomel (jsuchome) Feature #313142, revision 21 Title: YaST support only SSSD for LDAP based authentication - openSUSE Distribution: Ready + openSUSE Distribution: Done Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Ralf Haferkamp (rhafer) Partner organization: openSUSE.org Description: We should remove support for nss_ldap and pam_ldap configuration from the YaST ldap-client module (note: this is not a request to remove nss_ldap and pam_ldap from the distribution) and only support SSSD for LDAP based users authentication. The nss_ldap and pam_ldap packages should still be part of future distribution to still allow manual setup. When updating an nss-/pam_ldap based system from an older release it should stay with nss-/pam_ldap. Upon first startup of yast2-ldap-client it might offer a migration to sssd. Business case (Partner benefit): openSUSE.org: Focussing on a single implementation for LDAP authentication allows us to provide a cleaner UI and should reduce the complexity of the YaST ldap-client module considerably. Making it easier to use and maintain. Discussion: #1: Jiri Srain (jsrain) (2012-01-19 10:03:14) Joe, Matthias, this is in fact about removing existing functionality. How comon are the non-SSSD set-ups? #6: Jan Engelhardt (jengelh) (2012-01-23 22:36:15) (reply to #1) They can be migrated. #8: Lukas Ocilka (locilka) (2013-09-02 17:02:29) Jiri, please, go ahead and implement this feature. #9: Jiří Suchomel (jsuchome) (2013-09-03 15:54:41) Well, current yast2-ldap-client offers UI only for SSSD. If nss is detected, it will be rewritten to SSSD on exit. So I think this is what was requested. Ralf, could you confirm? Than we could close the feature. #10: Ralf Haferkamp (rhafer) (2013-09-05 10:05:58) (reply to #9) Yes. This can be closed as done already. -- openSUSE Feature: https://features.opensuse.org/313142