<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Restricting Access to Linux Servers after connecting to Active Directory in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/restricting-access-to-linux-servers-after-connecting-to-active/m-p/5654905#M53663</link>
    <description>&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have successfully connected my RH 5.8 servers to AD using Winbind. The problem is now anyone in AD can connect to the RH server. I need to allow only web developers to connect from different offices around the world. An AD solution is unlikely.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Fred&lt;/P&gt;</description>
    <pubDate>Fri, 11 May 2012 14:38:20 GMT</pubDate>
    <dc:creator>Fred Abell</dc:creator>
    <dc:date>2012-05-11T14:38:20Z</dc:date>
    <item>
      <title>Restricting Access to Linux Servers after connecting to Active Directory</title>
      <link>https://community.hpe.com/t5/operating-system-linux/restricting-access-to-linux-servers-after-connecting-to-active/m-p/5654905#M53663</link>
      <description>&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have successfully connected my RH 5.8 servers to AD using Winbind. The problem is now anyone in AD can connect to the RH server. I need to allow only web developers to connect from different offices around the world. An AD solution is unlikely.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Fred&lt;/P&gt;</description>
      <pubDate>Fri, 11 May 2012 14:38:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/restricting-access-to-linux-servers-after-connecting-to-active/m-p/5654905#M53663</guid>
      <dc:creator>Fred Abell</dc:creator>
      <dc:date>2012-05-11T14:38:20Z</dc:date>
    </item>
    <item>
      <title>Re: Restricting Access to Linux Servers after connecting to Active Directory</title>
      <link>https://community.hpe.com/t5/operating-system-linux/restricting-access-to-linux-servers-after-connecting-to-active/m-p/5656569#M53667</link>
      <description>&lt;P&gt;In AD, your web developers are probably distinguishable by being members of a particular group. Or you could request the AD admins to create a group for the purpose. Having a separate group might be useful if you someday need to allow someone who is not a web developer to access the Linux servers, or you'll have a web developer which must not be allowed to access the Linux servers for some reason.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That group should be automatically mapped to a Linux group by winbind: use that group in your access control configuration for all relevant services, so that the login attempt will be rejected if the user does not belong to that particular group.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You could apply this either at the server level (for example, SSH has DenyGroups/AllowGroups directives available in /etc/ssh/sshd_config file), or at the PAM level using the pam_succeed_if module (see "man pam_succeed_if").&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Something like this at the appropriate location in /etc/pam.d/system-auth might be what you're looking for:&lt;/P&gt;&lt;PRE&gt;auth required pam_succeed_if.so user ingroup &amp;lt;web_developers_group&amp;gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;Remember that the order of lines in PAM configuration files is meaningful.&lt;/P&gt;</description>
      <pubDate>Mon, 14 May 2012 07:52:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/restricting-access-to-linux-servers-after-connecting-to-active/m-p/5656569#M53667</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2012-05-14T07:52:17Z</dc:date>
    </item>
    <item>
      <title>Re: Restricting Access to Linux Servers after connecting to Active Directory</title>
      <link>https://community.hpe.com/t5/operating-system-linux/restricting-access-to-linux-servers-after-connecting-to-active/m-p/5657363#M53668</link>
      <description>&lt;P&gt;MK,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for responding. Unfortunately, there is no particular AD group to use. Users are scattered all over the world and isolating them via AD is impossible.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Fred&lt;/P&gt;</description>
      <pubDate>Mon, 14 May 2012 15:39:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/restricting-access-to-linux-servers-after-connecting-to-active/m-p/5657363#M53668</guid>
      <dc:creator>Fred Abell</dc:creator>
      <dc:date>2012-05-14T15:39:15Z</dc:date>
    </item>
    <item>
      <title>Re: Restricting Access to Linux Servers after connecting to Active Directory</title>
      <link>https://community.hpe.com/t5/operating-system-linux/restricting-access-to-linux-servers-after-connecting-to-active/m-p/5657659#M53669</link>
      <description>&lt;P&gt;Having discussed this further, I think the AD way is the only way to restrict access.&lt;/P&gt;</description>
      <pubDate>Mon, 14 May 2012 22:24:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/restricting-access-to-linux-servers-after-connecting-to-active/m-p/5657659#M53669</guid>
      <dc:creator>Fred Abell</dc:creator>
      <dc:date>2012-05-14T22:24:56Z</dc:date>
    </item>
  </channel>
</rss>

