- This topic has 0 replies, 1 voice, and was last updated 21 years, 1 month ago by
.
-
Posts
-
We’re getting by with openldap (standard RFC 2307) until we can roll the funds together to buy an OpenDirectory Server, but until then we’re seeing some strange things with Tiger. When a user logs into our machines, they get authorized via our local openldap server, but from a different kerberos server across campus.
From what I understand, the services in Tiger are all kerberized on the client and the server, but when a user with a network account logs remotely in via ssh (and possibly sudo), the user login will hang in /etc/pam.d/pam_secureserver.so. A successive login attempt or any uid/gid call that is not cached will pretty much lock the machine right up and force a reboot. My users really like to remote ssh into their Power Macs and iMacs, so I’m hoping to find a solution for this.
Has anyone ever seen this before? I suspect it might be because Tiger client is looking for an Open Directory component in openldap, or in some other protocol and doesn’t find it.
- You must be logged in to reply to this topic.