Grouper Users - Open Discussion List

[Tom Poage <>]

Hi, Michael.

That'd be close.

Something tells me to add one level of indirection, though that may be 
because I don't completely understand Grouper capabilities yet.

E.g. let's say I want to restrict ssh access to SIS servers to the set of 
sysadmins. Somewhere in there I might want to model a group containing the 
pool of servers which come and go over time, and another group of individuals 
belonging to the sysadmin group, likewise who come and go.

Maybe the simple thing to do is forget the servers and simply push (CFEngine, 
Puppet, ...) the "plussed" NIS group to /etc/password on subject servers with 
e.g.

+@sysadmin::0:0:::

making 'sysadmin' membership dynamic (say, Grouper-fed LDAP), and leave it at 
that. Not pretty, but perhaps functional.

Thanks.
Tom.

> On Dec 27, 2016, at 1:02 PM, Michael R. Gettes 
> <>
>  wrote:
> 
> Hi Tom,
> 
> Would the name of the group having the hostname and the group itself being 
> the population do the trick?
> 
> App:Unix:Netgroup:x.y.edu or something else to your liking?  The resulting 
> group could, of course, be the by product of other reference groups and 
> include/exclude compositing to support allow/deny scenarios.
> 
> /mrg
> 
>> On Dec 27, 2016, at 11:22, Tom Poage 
>> <>
>>  wrote:
>> 
>> Morning,
>> 
>> Grouper newbie.
>> 
>> Anyone gone to the effort of modeling NIS netgroups in Grouper? I.e.
>> 
>> name (user,machine,domain) (user,machine,domain) ...
>> 
>> I think we could do without the domain, so it'd basically be the 
>> intersection of groups of machines and groups of users.
>> 
>> If so, what did the model look like, and did you build an adapter to 
>> create the NIS map directly, or e.g. push to LDAP?
>> 
>> Of course, there are several other ways to accomplish authZ for shell 
>> access, such as SSSD w/ PAM, ....
>> 
>> Thanks.
>> Tom.
>