FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Directory

 
 
LinkBack Thread Tools
 
Old 02-15-2012, 11:30 PM
Gilbert Martin
 
Default help - Host Access Based on Group Membership

Hi,
I would like to control host access via groups/role? Has anyone done this? If so, can you give me some pointers in the correct direction?*
I've done my own research, but found that I need to allow more than one group to log into a system. So, pam_groupdn is out of the question. The other way of doing it would be to use SSH, but this involves a lot of client configuration. The 3rd option would be to use a netgroup style in 389.*

Please advice???
Thanks!*
--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
 
Old 02-16-2012, 02:12 PM
"Groten, Ryan"
 
Default help - Host Access Based on Group Membership

On RedHat Linux I did this by adding an entry to /etc/security/access.conf to allow certain groups to login.

Â*

Here’s what mine looks like:

Â*

# grep -v ^# /etc/security/access.conf

Â*

+ : safull sagroup2 : ALL

- : saldap : ALL

Â*

Safull is the group that is allowed access to that server, I also put every LDAP users into saldap so by default no ldap account has access to this server (unless
in safull or sagroup2).

Â*

You’ll need to add a line something like this to system-auth (or module specific file if you’re using it):

Â*

accountÂ*Â*Â*Â* requiredÂ*Â*Â*Â*Â* pam_access.so

Â*


From: 389-users-bounces@lists.fedoraproject.org [mailto:389-users-bounces@lists.fedoraproject.org]
On Behalf Of Gilbert Martin

Sent: Wednesday, February 15, 2012 5:31 PM

To: 389-users@lists.fedoraproject.org

Subject: [389-users] help - Host Access Based on Group Membership


Â*

Hi,


Â*



I would like to control host access via groups/role? Has anyone done this? If so, can you give me some pointers in the correct direction?Â*



Â*



I've done my own research, but found that I need to allow more than one group to log into a system. So, pam_groupdn is out of the question. The other way of doing it would be to use SSH, but this involves a lot of client configuration.
The 3rd option would be to use a netgroup style in 389.Â*



Â*



Please advice???



Â*



Thanks!Â*






This communication, including any attached documentation, is intended only for the person or entity to which it is addressed, and may contain confidential, personal and/or privileged information. Any unauthorized disclosure,
copying, or taking action on the contents is strictly prohibited. If you have received this message in error, please contact us immediately so we may correct our records. Please then delete or destroy the original transmission and any subsequent reply.




--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
 

Thread Tools




All times are GMT. The time now is 05:57 AM.

VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org