I'm trying to bind a 10.4 box to an existing NIS domain, and all seems happy excpet that when a user logs in, the account is not put in all the correct groups.
For example, in our NIS passwd map it shows that a user (let's call him USER-A) has a default group (gid) of GROUP-A. In our NIS groups map, there are other groups (GROUP-B, GROUP-C, etc.) that also list the user as a member of those groups. When the user logs in via ssh, and types 'groups' or 'id' at the command prompt, it shows that the user is a part of GROUP-A, but not a part of GROUP-B or GROUP-C.
I can do a 'ypmatch GROUP-B group' and see that the NIS map shows that the user should be a part of it, and groups are reported correctly in file listings.
The problem this creates is that we have NFS directories that are permission-controlled by groups. So if a user is not in a particular group, they cannot get access to their files. Because of our structure, a user must belong to several groups at once.
Is anyone else having this difficulty with NIS? Has anyone gotten this to work?
Thanks for any advice!
For example, in our NIS passwd map it shows that a user (let's call him USER-A) has a default group (gid) of GROUP-A. In our NIS groups map, there are other groups (GROUP-B, GROUP-C, etc.) that also list the user as a member of those groups. When the user logs in via ssh, and types 'groups' or 'id' at the command prompt, it shows that the user is a part of GROUP-A, but not a part of GROUP-B or GROUP-C.
I can do a 'ypmatch GROUP-B group' and see that the NIS map shows that the user should be a part of it, and groups are reported correctly in file listings.
The problem this creates is that we have NFS directories that are permission-controlled by groups. So if a user is not in a particular group, they cannot get access to their files. Because of our structure, a user must belong to several groups at once.
Is anyone else having this difficulty with NIS? Has anyone gotten this to work?
Thanks for any advice!