<?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 In 6.2.0 the header name is in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/fmc-rest-api-6-1/m-p/2946305#M1029429</link>
    <description>&lt;P&gt;In 6.2.0 the header name is lowercase 'domains'.&lt;/P&gt;</description>
    <pubDate>Wed, 08 Mar 2017 11:03:56 GMT</pubDate>
    <dc:creator>Alexander Hartmaier</dc:creator>
    <dc:date>2017-03-08T11:03:56Z</dc:date>
    <item>
      <title>FMC REST API 6.1</title>
      <link>https://community.cisco.com/t5/network-security/fmc-rest-api-6-1/m-p/2946300#M1029424</link>
      <description>&lt;P&gt;I am currently playing around with firepower rest api on FMC 6.1 and I am looking for a method to get&amp;nbsp;domain name to domain id mapping. Since the specific domain id must be used in the URL to consume&amp;nbsp;the api I would like to get the ID by name.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://fmc.example.com/api/fmc_platform/v1/domain/" target="_blank"&gt;https://fmc.example.com/api/fmc_platform/v1/domain/&lt;/A&gt;&lt;STRONG&gt;&amp;lt;domainid&amp;gt;&lt;/STRONG&gt;/&amp;lt;operation&amp;gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Please let me know if there is a way to do this atm. Since the api-explorer provides a dropdown to select the correct domain I think this should be possible.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;kind regards&lt;/P&gt;
&lt;P&gt;Oliver&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 13:54:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-rest-api-6-1/m-p/2946300#M1029424</guid>
      <dc:creator>Oliver Kaiser</dc:creator>
      <dc:date>2020-02-21T13:54:54Z</dc:date>
    </item>
    <item>
      <title>After reading docs and using</title>
      <link>https://community.cisco.com/t5/network-security/fmc-rest-api-6-1/m-p/2946301#M1029425</link>
      <description>&lt;P&gt;After reading docs and using the API for quite some time, I have concluded that this is not possible atm or not documented... Hoping for 6.2 to fix this issue.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Oct 2016 18:12:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-rest-api-6-1/m-p/2946301#M1029425</guid>
      <dc:creator>Oliver Kaiser</dc:creator>
      <dc:date>2016-10-27T18:12:47Z</dc:date>
    </item>
    <item>
      <title>I checked and its not in the</title>
      <link>https://community.cisco.com/t5/network-security/fmc-rest-api-6-1/m-p/2946302#M1029426</link>
      <description>&lt;P&gt;I checked and its not in the 6.2 release. &amp;nbsp;I've asked about the following release. .. TBD&lt;/P&gt;</description>
      <pubDate>Thu, 27 Oct 2016 20:08:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-rest-api-6-1/m-p/2946302#M1029426</guid>
      <dc:creator>dohurd</dc:creator>
      <dc:date>2016-10-27T20:08:58Z</dc:date>
    </item>
    <item>
      <title>I did get some more insight</title>
      <link>https://community.cisco.com/t5/network-security/fmc-rest-api-6-1/m-p/2946303#M1029427</link>
      <description>&lt;P&gt;I did get some more insight that may be helpful:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;When you retrieve the token, the domains uuids for which the user is authorized are sent in the HTTP header along with the tokens.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;When you run a post to the following URI:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p2"&gt;&lt;SPAN class="s2"&gt;&lt;A href="https://[FMCIP]/api/fmc_platform/v1/auth/generatetoken"&gt;https://[FMCIP]/api/fmc_platform/v1/auth/generatetoken&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;using your API credentials (username and password), the return headers will include DOMAIN details. The example below has the domain highlighted. As Kirti said this is the domain the user is authorized to login to so it can be used to quickly and easily identify which domain you are making calls to.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p1"&gt;&lt;SPAN class="s1"&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p3"&gt;&lt;SPAN class="s1"&gt;&lt;B&gt;Accept-Ranges&amp;nbsp;&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s3"&gt;&lt;B&gt;→&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s1"&gt;bytes&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p3"&gt;&lt;SPAN class="s1"&gt;&lt;B&gt;Cache-Control&amp;nbsp;&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s3"&gt;&lt;B&gt;→&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s1"&gt;no-cache, no-store, must-revalidate, max-age=0&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p3"&gt;&lt;SPAN class="s1"&gt;&lt;B&gt;Connection&amp;nbsp;&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s3"&gt;&lt;B&gt;→&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s1"&gt;Keep-Alive&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p3"&gt;&lt;SPAN class="s1"&gt;&lt;B&gt;Content-Length&amp;nbsp;&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s3"&gt;&lt;B&gt;→&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s1"&gt;0&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p3"&gt;&lt;SPAN class="s4"&gt;&lt;B&gt;DOMAINS&amp;nbsp;&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s5"&gt;&lt;B&gt;→&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s4"&gt;[{"name":"Global","uuid":"e276abec-e0f2-11e3-8169-6d9ed49b625f"}]&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p3"&gt;&lt;SPAN class="s1"&gt;&lt;B&gt;DOMAIN_ID&amp;nbsp;&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s3"&gt;&lt;B&gt;→&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s1"&gt;111&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p3"&gt;&lt;SPAN class="s1"&gt;&lt;B&gt;DOMAIN_UUID&amp;nbsp;&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s3"&gt;&lt;B&gt;→&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s1"&gt;e276abec-e0f2-11e3-8169-6d9ed49b625f&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p3"&gt;&lt;SPAN class="s1"&gt;&lt;B&gt;Date&amp;nbsp;&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s3"&gt;&lt;B&gt;→&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s1"&gt;Fri, 28 Oct 2016 12:45:42 GMT&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p3"&gt;&lt;SPAN class="s1"&gt;&lt;B&gt;Keep-Alive&amp;nbsp;&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s3"&gt;&lt;B&gt;→&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s1"&gt;timeout=5, max=100&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p3"&gt;&lt;SPAN class="s1"&gt;&lt;B&gt;Server&amp;nbsp;&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s3"&gt;&lt;B&gt;→&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s1"&gt;Apache&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p3"&gt;&lt;SPAN class="s1"&gt;&lt;B&gt;USER_UUID&amp;nbsp;&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s3"&gt;&lt;B&gt;→&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s1"&gt;9fcaa802-742f-11e6-940a-dcadeeddb529&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p3"&gt;&lt;SPAN class="s1"&gt;&lt;B&gt;Vary&amp;nbsp;&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s3"&gt;&lt;B&gt;→&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s1"&gt;Accept-Charset,Accept-Encoding,Accept-Language,Accept&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p3"&gt;&lt;SPAN class="s1"&gt;&lt;B&gt;X-Frame-Options&amp;nbsp;&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s3"&gt;&lt;B&gt;→&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s1"&gt;SAMEORIGIN&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p3"&gt;&lt;SPAN class="s1"&gt;&lt;B&gt;X-auth-access-token&amp;nbsp;&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s3"&gt;&lt;B&gt;→&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s1"&gt;bfc90e8e-6893-4cc6-a82f-3b6579b13444&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p3"&gt;&lt;SPAN class="s1"&gt;&lt;B&gt;X-auth-refresh-token&amp;nbsp;&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s3"&gt;&lt;B&gt;→&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s1"&gt;6c0bbbbb-2550-47c3-a165-20c0ee28e470&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="p3"&gt;&lt;SPAN class="s1"&gt;&lt;B&gt;global&amp;nbsp;&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s3"&gt;&lt;B&gt;→&lt;/B&gt;&lt;/SPAN&gt;&lt;SPAN class="s1"&gt;e276abec-e0f2-11e3-8169-6d9ed49b625f&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Oct 2016 12:51:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-rest-api-6-1/m-p/2946303#M1029427</guid>
      <dc:creator>dohurd</dc:creator>
      <dc:date>2016-10-28T12:51:19Z</dc:date>
    </item>
    <item>
      <title>Thanks a lot for taking the</title>
      <link>https://community.cisco.com/t5/network-security/fmc-rest-api-6-1/m-p/2946304#M1029428</link>
      <description>&lt;P&gt;Thanks a lot for taking the time, I have tested it and found the domain mappings in the header of the authtoken request as you mentioned!&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Oct 2016 22:51:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-rest-api-6-1/m-p/2946304#M1029428</guid>
      <dc:creator>Oliver Kaiser</dc:creator>
      <dc:date>2016-10-28T22:51:09Z</dc:date>
    </item>
    <item>
      <title>In 6.2.0 the header name is</title>
      <link>https://community.cisco.com/t5/network-security/fmc-rest-api-6-1/m-p/2946305#M1029429</link>
      <description>&lt;P&gt;In 6.2.0 the header name is lowercase 'domains'.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Mar 2017 11:03:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-rest-api-6-1/m-p/2946305#M1029429</guid>
      <dc:creator>Alexander Hartmaier</dc:creator>
      <dc:date>2017-03-08T11:03:56Z</dc:date>
    </item>
  </channel>
</rss>

