https://bugzilla.novell.com/show_bug.cgi?id=345965
User rhafer@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=345965#c7
Ralf Haferkamp
(In reply to comment #5 from Ralf Haferkamp)
What needs to be done from client sude if the "support" is currently missing? You should inform the user about that and check the "pam_lookup_policy" value in /etc/ldap.conf.
I don't understand. If client should not change the server configuration (as stated above), than it should probably not even edit ldap.conf regarding the LDAP policy, right? I probably missunderstood the original question, but I thougt the client was already configured to handle password policies and then something on the server was change. (In that case it would make sense to inform the user about the fact, that there seems to be a missconfiguration). During the initial setup I agree, if the client detect, that the server does not support ppolicy. It should not change the ldap.conf regarding ppolicy.
We are in the situation where there is still no support at server side. I assume that the client should just disable the widgets for editing password policy objects (+ maybe inform user to configure it on server), right? Yep.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.