<?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: Timeout on Duo auth API in APIs</title>
    <link>https://community.cisco.com/t5/apis/timeout-on-duo-auth-api/m-p/4882098#M420</link>
    <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;Any solution for this problem (after two years)?&lt;BR /&gt;
I’m facing the exact same problem and see a couple of similar threads, but none with an actual answer.&lt;/P&gt;
&lt;P&gt;And please note: &lt;EM&gt;“no”&lt;/EM&gt; is also an answer, but leaving things open like this is pretty frustrating, specially when more people are having the same issue.&lt;/P&gt;
&lt;P&gt;I’m using Delphi with Indy btw, but the results are exactly the same as above (and other) threads.&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Peter&lt;/P&gt;&lt;/DIV&gt;</description>
    <pubDate>Fri, 04 Dec 2020 14:11:35 GMT</pubDate>
    <dc:creator>QuickFix</dc:creator>
    <dc:date>2020-12-04T14:11:35Z</dc:date>
    <item>
      <title>Timeout on Duo auth API</title>
      <link>https://community.cisco.com/t5/apis/timeout-on-duo-auth-api/m-p/4882095#M417</link>
      <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;I’m creating a “send duo push” function for our helpdesk to help with identity proofing customers over the phone (I know there is now one in the console, but thats a different story).   When I call the auth API there seems to be a 10 second timeout.  I would like to adjust this timeout to something more reasonable, like 30 seconds.  How can I do that? I don’t see that documented, but you would think it would be a basic feature.&lt;/P&gt;
&lt;ASIDE class="onebox whitelistedgeneric"&gt;
  &lt;HEADER class="source"&gt;
      &lt;IMG src="https://duo.com/favicon.ico" class="site-icon" width="32" height="32" /&gt;
      &lt;A href="https://duo.com/docs/authapi#/auth" target="_blank" rel="nofollow noopener"&gt;Duo Security&lt;/A&gt;
  &lt;/HEADER&gt;
  &lt;ARTICLE class="onebox-body"&gt;
    &lt;DIV class="aspect-image" style="--aspect-ratio:690/362;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="1X_2bd75a973c77e6a95501f3d6c53b011eb408f1cb.jpeg"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/190816iD9AD0002343E97AC/image-size/large?v=v2&amp;amp;px=999" role="button" title="1X_2bd75a973c77e6a95501f3d6c53b011eb408f1cb.jpeg" alt="1X_2bd75a973c77e6a95501f3d6c53b011eb408f1cb.jpeg" /&gt;&lt;/span&gt;&lt;/DIV&gt;

&lt;H3&gt;&lt;A href="https://duo.com/docs/authapi#/auth" target="_blank" rel="nofollow noopener"&gt;Auth API&lt;/A&gt;&lt;/H3&gt;

&lt;P&gt;The Auth API is a low-level, RESTful API for adding strong two-factor authentication to your website or application. Learn more.&lt;/P&gt;


  &lt;/ARTICLE&gt;
  &lt;DIV class="onebox-metadata"&gt;
    
    
  &lt;/DIV&gt;
  &lt;DIV style="clear: both"&gt;&lt;/DIV&gt;
&lt;/ASIDE&gt;

&lt;P&gt;Thanks!&lt;/P&gt;
&lt;P&gt;Todd&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 25 Oct 2018 19:28:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/apis/timeout-on-duo-auth-api/m-p/4882095#M417</guid>
      <dc:creator>Todd_Haddaway</dc:creator>
      <dc:date>2018-10-25T19:28:34Z</dc:date>
    </item>
    <item>
      <title>Re: Timeout on Duo auth API</title>
      <link>https://community.cisco.com/t5/apis/timeout-on-duo-auth-api/m-p/4882096#M418</link>
      <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;If your intent is to give the user more time to approve the authentication request, try using the &lt;CODE&gt;async&lt;/CODE&gt; parameter, and then poll &lt;A href="https://duo.com/docs/authapi#/auth_status"&gt;/auth_status&lt;/A&gt; for completion.&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 25 Oct 2018 20:32:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/apis/timeout-on-duo-auth-api/m-p/4882096#M418</guid>
      <dc:creator>DuoKristina</dc:creator>
      <dc:date>2018-10-25T20:32:16Z</dc:date>
    </item>
    <item>
      <title>Re: Timeout on Duo auth API</title>
      <link>https://community.cisco.com/t5/apis/timeout-on-duo-auth-api/m-p/4882097#M419</link>
      <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;I have tried that and am getting different results than I expected.  My expected behavior is that I call the auth endpoint (with async) - that sends the push out.  Afterwards I can call the auth_status periodically and will get “waiting” returned until such time as the user either approves or denies.  Given the code below, I am still getting a timeout.  See code and results below:&lt;/P&gt;
&lt;P&gt;code&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class="lang-auto"&gt;    $authConnection = getAuthConnection();
    $factorParams = array("device"=&amp;gt;"auto","type"=&amp;gt;"UMBC TSC",null,"pushinfo"=&amp;gt;"from=UMBC%20Technology%20Support%20Center&amp;amp;Purpose=Identity%20Validation");

         print "*** Sending Push: " . date('Y-m-d H:i:s') . "\n";
		$PushResult = sendAsyncPush($authConnection);		
		print_r($PushResult);
		$txid = $PushResult["response"]["response"]["txid"];
		
        print "*** Calling auth_status 1 of 2 " . date('Y-m-d H:i:s') . "\n";
		$PushResult = $authConnection-&amp;gt;auth_status($txid);
		print_r($PushResult);

        print "*** Calling auth_status 2 of 2 " . date('Y-m-d H:i:s') . "\n";
		$PushResult = $authConnection-&amp;gt;auth_status($txid);
		print_r($PushResult);

        print "*** done " . date('Y-m-d H:i:s') . "\n";

&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;Executing this gives the following results:&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class="lang-auto"&gt;    
*** Sending Push: 2018-10-26 11:00:59
Array
(
    [response] =&amp;gt; Array
        (
            [response] =&amp;gt; Array
                (
                    [txid] =&amp;gt; 12345-12345-12345-12345-12345
                )

            [stat] =&amp;gt; OK
        )

    [success] =&amp;gt; 1
    [http_status_code] =&amp;gt; 200
)
*** Calling auth_status 1 of 2 2018-10-26 11:01:00
Array
(
    [response] =&amp;gt; Array
        (
            [response] =&amp;gt; Array
                (
                    [result] =&amp;gt; waiting
                    [status] =&amp;gt; pushed
                    [status_msg] =&amp;gt; Pushed a login request to your device...
                )

            [stat] =&amp;gt; OK
        )

    [success] =&amp;gt; 1
    [http_status_code] =&amp;gt; 200
)
*** Calling auth_status 2 of 2 2018-10-26 11:01:00
Array
(
    [response] =&amp;gt; Array
        (
            [stat] =&amp;gt; FAIL
            [code] =&amp;gt; 28
            [message] =&amp;gt; Operation timed out after 10001 milliseconds with 0 out of -1 bytes received
        )

    [success] =&amp;gt;
    [http_status_code] =&amp;gt;
)
*** done 2018-10-26 11:01:10```&lt;/CODE&gt;&lt;/PRE&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 26 Oct 2018 00:01:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/apis/timeout-on-duo-auth-api/m-p/4882097#M419</guid>
      <dc:creator>Todd_Haddaway</dc:creator>
      <dc:date>2018-10-26T00:01:08Z</dc:date>
    </item>
    <item>
      <title>Re: Timeout on Duo auth API</title>
      <link>https://community.cisco.com/t5/apis/timeout-on-duo-auth-api/m-p/4882098#M420</link>
      <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;Any solution for this problem (after two years)?&lt;BR /&gt;
I’m facing the exact same problem and see a couple of similar threads, but none with an actual answer.&lt;/P&gt;
&lt;P&gt;And please note: &lt;EM&gt;“no”&lt;/EM&gt; is also an answer, but leaving things open like this is pretty frustrating, specially when more people are having the same issue.&lt;/P&gt;
&lt;P&gt;I’m using Delphi with Indy btw, but the results are exactly the same as above (and other) threads.&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Peter&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 04 Dec 2020 14:11:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/apis/timeout-on-duo-auth-api/m-p/4882098#M420</guid>
      <dc:creator>QuickFix</dc:creator>
      <dc:date>2020-12-04T14:11:35Z</dc:date>
    </item>
    <item>
      <title>Re: Timeout on Duo auth API</title>
      <link>https://community.cisco.com/t5/apis/timeout-on-duo-auth-api/m-p/4882099#M421</link>
      <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;Hey &lt;A class="mention" href="https://community.duo.com/u/quickfix"&gt;@QuickFix&lt;/A&gt;,&lt;/P&gt;
&lt;P&gt;I think there might be a misunderstanding with how the &lt;CODE&gt;/auth_status&lt;/CODE&gt; endpoint is used.&lt;/P&gt;
&lt;P&gt;When a Duo Push is initiated via the /auth endpoint and the &lt;CODE&gt;async&lt;/CODE&gt; parameter, we will immediately send a ‘pushed/waiting’ status, which can be pulled via &lt;CODE&gt;/auth_status&lt;/CODE&gt; right away. The status is not updated again for a particular authentication attempted until it is either answered with an approve/deny or it times out.&lt;/P&gt;
&lt;P&gt;One recommendation is to make sure that your application has a 60-second timeout configured, as this is the defined timeout for a Duo Push. You could then use &lt;CODE&gt;/auth_status&lt;/CODE&gt; once during the transaction to check if the request is still waiting or if the user has actioned it.&lt;/P&gt;
&lt;P&gt;Thanks!&lt;BR /&gt;
Colin&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 16 Dec 2020 21:29:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/apis/timeout-on-duo-auth-api/m-p/4882099#M421</guid>
      <dc:creator>colin_medfisch</dc:creator>
      <dc:date>2020-12-16T21:29:04Z</dc:date>
    </item>
    <item>
      <title>Re: Timeout on Duo auth API</title>
      <link>https://community.cisco.com/t5/apis/timeout-on-duo-auth-api/m-p/4882100#M422</link>
      <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;Thanks for your answer &lt;A class="mention" href="https://community.duo.com/u/cmedfischduo"&gt;@cmedfischduo&lt;/A&gt;,&lt;/P&gt;
&lt;P&gt;The problem with normal (single threaded) applications is that waiting on a (any) reply will stall the entire application.&lt;BR /&gt;
I fixed my problem by putting all DUO requests into separate threads, which will keep the application responsive and can be killed in the event a user wants to cancel authenticating.&lt;/P&gt;
&lt;P&gt;Thanks again for your reply,&lt;/P&gt;
&lt;P&gt;Peter&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 17 Dec 2020 07:56:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/apis/timeout-on-duo-auth-api/m-p/4882100#M422</guid>
      <dc:creator>QuickFix</dc:creator>
      <dc:date>2020-12-17T07:56:20Z</dc:date>
    </item>
  </channel>
</rss>

