<?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: Is the e-directiry agent 3.1 able to authenticate communications with clients? in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/is-the-e-directiry-agent-3-1-able-to-authenticate-communications/m-p/22809#M16670</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There isn't currently any authentication within the API. However there is the ability within the agent to specify a list of hosts that are allowed to use the API. Entering the specific source IP addresses of hosts that will use the API will block any connections for other IP addresses.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 03 Apr 2010 03:34:31 GMT</pubDate>
    <dc:creator>mjacobsen</dc:creator>
    <dc:date>2010-04-03T03:34:31Z</dc:date>
    <item>
      <title>Is the e-directiry agent 3.1 able to authenticate communications with clients?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/is-the-e-directiry-agent-3-1-able-to-authenticate-communications/m-p/22808#M16669</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;We are planning to use the XML API. And i noticed that it requires an ssl communications between clients and the agent. I want to know if the agent is able to authenticate communication with client. And if not, is there any plan to implement this functionnality in future releases.&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Apr 2010 07:49:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/is-the-e-directiry-agent-3-1-able-to-authenticate-communications/m-p/22808#M16669</guid>
      <dc:creator>asia</dc:creator>
      <dc:date>2010-04-02T07:49:51Z</dc:date>
    </item>
    <item>
      <title>Re: Is the e-directiry agent 3.1 able to authenticate communications with clients?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/is-the-e-directiry-agent-3-1-able-to-authenticate-communications/m-p/22809#M16670</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There isn't currently any authentication within the API. However there is the ability within the agent to specify a list of hosts that are allowed to use the API. Entering the specific source IP addresses of hosts that will use the API will block any connections for other IP addresses.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 03 Apr 2010 03:34:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/is-the-e-directiry-agent-3-1-able-to-authenticate-communications/m-p/22809#M16670</guid>
      <dc:creator>mjacobsen</dc:creator>
      <dc:date>2010-04-03T03:34:31Z</dc:date>
    </item>
    <item>
      <title>Re: Is the e-directiry agent 3.1 able to authenticate communications with clients?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/is-the-e-directiry-agent-3-1-able-to-authenticate-communications/m-p/22810#M16671</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for this answer. But it is important to us that this functionnality be present in future releases, can you tell me if there is a plan to implement it?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Apr 2010 09:20:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/is-the-e-directiry-agent-3-1-able-to-authenticate-communications/m-p/22810#M16671</guid>
      <dc:creator>asia</dc:creator>
      <dc:date>2010-04-06T09:20:26Z</dc:date>
    </item>
  </channel>
</rss>

