Hi all,
I work in a mid-sized department inside a big organization and I have a question regarding authentication.
Currently, our department gives all linux users a username and password for their computing accounts that is separate from their other ID and Password.
We now want to move to the organization's central IT authentication to get out of the password business and to provide users with a single sign-on solution.
Our organization uses Kerberos + LDAP for authentication/authorization.
I've set up a test machine and it works - anyone with a valid organization ID and password can log in. Therein lies the problem!
I don't want everyone to be able to log in, only those in our department. How do I restrict or impose further security so that only our department's users can gain authentication and log in to the machine?

Thanks for any help!

Well that depends what data you have to separate your department from others... how do you know the difference in the first place? in a centralized system I'd expect that to be ldap group membership from what you say so far. is that right? If so there are plenty of ways, like configuring group requirements in /etc/security/access.conf on most systems. This can also be pushed slightly upstream into the pam config files themselves if need be.

Chris,
I'm not sure if I follow your train of thought but allow me to clarify.
So everyone in the entire organization has a login ID and password. Our department has only 100 people. I only want those 100 people (whose ID's I know) to be able to log in to our machines and be able to work as they usually do.
I guess I'm not entirely familiar with the authentication process or what resources are available to allow me to create a group or how this all ties together.
If I have a list of our 100 people's user ID's, I would like them to be able to:
#1 - log in to the machine/s
#2 - own their files and have memberships to the NIS groups that are currently set up
Thanks for your guidance!