<?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 Not completely , You can use in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/sourcefire-user-agent-and-ldap-integration/m-p/2944678#M161393</link>
    <description>&lt;P&gt;Not completely , You can use virtual ip but&amp;nbsp; still yor authentication is stil from citrix servet. not from virtual ip desktop&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 08 Dec 2016 12:01:26 GMT</pubDate>
    <dc:creator>jacek99111</dc:creator>
    <dc:date>2016-12-08T12:01:26Z</dc:date>
    <item>
      <title>Sourcefire User Agent and LDAP integration</title>
      <link>https://community.cisco.com/t5/network-security/sourcefire-user-agent-and-ldap-integration/m-p/2944675#M161386</link>
      <description>&lt;P&gt;Does anyone have any experience using LDAP integration with the Firepower/Firesight setup (ASA with integrated firepower, managed via Firesight) that uses rules containing Active Directory groups and Citrix? &amp;nbsp;I see the sourcefire user agent's purpose is to map IP addresses to user accounts, so my concern is that the IP address of a Citrix server will be used in the rule if I have a user that is logged into that Citrix server hitting a particular rule, and wouldn't want that rule to apply to all users currently connected to that Citrix server.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;thank you,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Bill&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 08:02:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/sourcefire-user-agent-and-ldap-integration/m-p/2944675#M161386</guid>
      <dc:creator>WILLIAM STEGMAN</dc:creator>
      <dc:date>2019-03-12T08:02:46Z</dc:date>
    </item>
    <item>
      <title>There is no Citrix User Agent</title>
      <link>https://community.cisco.com/t5/network-security/sourcefire-user-agent-and-ldap-integration/m-p/2944676#M161388</link>
      <description>&lt;P&gt;There is no Citrix User Agent yet, so your other option would be&amp;nbsp;enable per-session IP Virtualization for your Citrix hosts.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;http://support.citrix.com/article/CTX137163&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;-Smalley&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jul 2016 21:57:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/sourcefire-user-agent-and-ldap-integration/m-p/2944676#M161388</guid>
      <dc:creator>Greg Smalley</dc:creator>
      <dc:date>2016-07-26T21:57:29Z</dc:date>
    </item>
    <item>
      <title>thanks Greg</title>
      <link>https://community.cisco.com/t5/network-security/sourcefire-user-agent-and-ldap-integration/m-p/2944677#M161390</link>
      <description>&lt;P&gt;thanks Greg&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jul 2016 15:00:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/sourcefire-user-agent-and-ldap-integration/m-p/2944677#M161390</guid>
      <dc:creator>WILLIAM STEGMAN</dc:creator>
      <dc:date>2016-07-27T15:00:36Z</dc:date>
    </item>
    <item>
      <title>Not completely , You can use</title>
      <link>https://community.cisco.com/t5/network-security/sourcefire-user-agent-and-ldap-integration/m-p/2944678#M161393</link>
      <description>&lt;P&gt;Not completely , You can use virtual ip but&amp;nbsp; still yor authentication is stil from citrix servet. not from virtual ip desktop&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 08 Dec 2016 12:01:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/sourcefire-user-agent-and-ldap-integration/m-p/2944678#M161393</guid>
      <dc:creator>jacek99111</dc:creator>
      <dc:date>2016-12-08T12:01:26Z</dc:date>
    </item>
  </channel>
</rss>

