<?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 API authentications failure logging in APIs</title>
    <link>https://community.cisco.com/t5/apis/api-authentications-failure-logging/m-p/4881593#M370</link>
    <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;Need authentication failures logging for DUO API into main Duo log for better troubleshooting.&lt;BR /&gt;
I have 2 different vendors pulling API for users and authentication logs, but as an admin I don’t see anything on Duo-admin page from which ip addresses API keys are used from. This raises a concern as there is no method to monitor access to Duo-API’s with Duo-Admin interface or 3rd party SEIM tools.&lt;/P&gt;&lt;/DIV&gt;</description>
    <pubDate>Tue, 06 Nov 2018 17:13:46 GMT</pubDate>
    <dc:creator>avs1</dc:creator>
    <dc:date>2018-11-06T17:13:46Z</dc:date>
    <item>
      <title>API authentications failure logging</title>
      <link>https://community.cisco.com/t5/apis/api-authentications-failure-logging/m-p/4881593#M370</link>
      <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;Need authentication failures logging for DUO API into main Duo log for better troubleshooting.&lt;BR /&gt;
I have 2 different vendors pulling API for users and authentication logs, but as an admin I don’t see anything on Duo-admin page from which ip addresses API keys are used from. This raises a concern as there is no method to monitor access to Duo-API’s with Duo-Admin interface or 3rd party SEIM tools.&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 06 Nov 2018 17:13:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/apis/api-authentications-failure-logging/m-p/4881593#M370</guid>
      <dc:creator>avs1</dc:creator>
      <dc:date>2018-11-06T17:13:46Z</dc:date>
    </item>
  </channel>
</rss>

