[Date Prev][Date Next]
Help with Solaris LDAP client (how to make client read shadow information)
- To: firstname.lastname@example.org
- Subject: Help with Solaris LDAP client (how to make client read shadow information)
- From: curious penguin <email@example.com>
- Date: Thu, 9 Feb 2012 17:32:06 -0800
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=VjEVX9qeq8s+5zj0CslAvhyHNm+I6fy6X9/VsBrmUc0=; b=MsvLb9MWbYpBRL6LZhofl1bzc01No/88Ssn+wiPfQObrgXPIhH9rCI1q6GHYimeDBV 6OXJg3Md5KeWSjbWoN17NIaXZbPf0RIpdU4f71P2T1NeMdlUJnwWOXP10cAU0St64TFh hL2tRn8JsGqAPp0FS+XlxBzoE0bQM0Gil1N4o=
I have ldap clients on two different OS platforms, Solaris and Linux.
When "shadowExpire" for a specific user is set, the Linux client sees
the change and denies logon for the user which is what I'm trying to
implement. But this behaviour doesn't work in my Solaris client. It
seems like it doesn't respect the rest of the shadow attributes on the
Ldap server. I've been scratching my head for days now but doing so
haven't help me figure out what the problem or reason is.
Could anyone shed some light on this.