<?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 Re: Security policy rule to whitelist social media category by AD security group - multi-domain in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/security-policy-rule-to-whitelist-social-media-category-by-ad/m-p/304899#M79246</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/55465"&gt;@ScottMacDonald&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;This should work perfectly fine. When you are creating the group mapping are you getting the list to propogate properly? If the answer is yes, you might want to look at your useridd.log file and see if you have any warnings corresponding to the group.&lt;/P&gt;</description>
    <pubDate>Wed, 25 Dec 2019 18:13:08 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2019-12-25T18:13:08Z</dc:date>
    <item>
      <title>Security policy rule to whitelist social media category by AD security group - multi-domain</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/security-policy-rule-to-whitelist-social-media-category-by-ad/m-p/304867#M79239</link>
      <description>&lt;P&gt;Trying to configure this rule to whitelist users in an AD security group that's in another domain in our forest. It works with our domain fine, but when I try to create an LDAP server profile for another domain, a group mapping with a group include list where I can drill down and see the AD security group that was created, after adding to the rule it's not being picking it up. For example, ourdomain\whitelist works but not otherdomain\whitelist.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was instructed to block social media and personal webmail url filtering categories and now certain people are freaking out, so I'm trying to whitelist people in a multi-domain environment. Please let me know if anyone has any ideas or recommendations.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Scott&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Dec 2019 19:14:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/security-policy-rule-to-whitelist-social-media-category-by-ad/m-p/304867#M79239</guid>
      <dc:creator>ScottMacDonald</dc:creator>
      <dc:date>2019-12-24T19:14:22Z</dc:date>
    </item>
    <item>
      <title>Re: Security policy rule to whitelist social media category by AD security group - multi-domain</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/security-policy-rule-to-whitelist-social-media-category-by-ad/m-p/304899#M79246</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/55465"&gt;@ScottMacDonald&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;This should work perfectly fine. When you are creating the group mapping are you getting the list to propogate properly? If the answer is yes, you might want to look at your useridd.log file and see if you have any warnings corresponding to the group.&lt;/P&gt;</description>
      <pubDate>Wed, 25 Dec 2019 18:13:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/security-policy-rule-to-whitelist-social-media-category-by-ad/m-p/304899#M79246</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2019-12-25T18:13:08Z</dc:date>
    </item>
  </channel>
</rss>

