<?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 Two-Factor Authentication Issues in Arlo</title>
    <link>https://community.arlo.com/t5/Arlo/Two-Factor-Authentication-Issues/m-p/1766400#M75296</link>
    <description>&lt;P&gt;I enabled the two-factor auth, and I have a couple of observations/suggestions that I hope the developers will consider.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;First, I strongly prefer TOTP authentication rather than SMS. SMS is better than nothing, but it has a lot of known weaknesses and inconveniences. I hope you will add TOTP as a two-factor code generation option in the future.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Second, the design of the iOS app, at least the current app I have installed (version 2.15) makes two-factor login unusable without two devices. Upon login, using iOS's touch ID, I was presented with a screen notifying me that a code had been texted to me, and a place to type the code. But I had to switch apps to view the code, and when I switched back to the Arlo app it had logged me out and restarted the login process, invalidating the code I was sent. Stuck in an infinite loop, I had to have the code emailed to me so I could view it on a different device and avoid being logged out mid-login.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Finally, and this is a minor issue, but there's something wrong with the design of the entry field for the two-factor code. You have to touch to start entering the code -- it is not focused by default -- and you can accidentally touch the second of the six boxes. It should be a single field, not six fields designed to appear as a single six-digit field.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I hope these suggestions are helpful!&lt;/P&gt;</description>
    <pubDate>Wed, 15 Apr 2020 14:14:27 GMT</pubDate>
    <dc:creator>xaprb</dc:creator>
    <dc:date>2020-04-15T14:14:27Z</dc:date>
    <item>
      <title>Two-Factor Authentication Issues</title>
      <link>https://community.arlo.com/t5/Arlo/Two-Factor-Authentication-Issues/m-p/1766400#M75296</link>
      <description>&lt;P&gt;I enabled the two-factor auth, and I have a couple of observations/suggestions that I hope the developers will consider.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;First, I strongly prefer TOTP authentication rather than SMS. SMS is better than nothing, but it has a lot of known weaknesses and inconveniences. I hope you will add TOTP as a two-factor code generation option in the future.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Second, the design of the iOS app, at least the current app I have installed (version 2.15) makes two-factor login unusable without two devices. Upon login, using iOS's touch ID, I was presented with a screen notifying me that a code had been texted to me, and a place to type the code. But I had to switch apps to view the code, and when I switched back to the Arlo app it had logged me out and restarted the login process, invalidating the code I was sent. Stuck in an infinite loop, I had to have the code emailed to me so I could view it on a different device and avoid being logged out mid-login.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Finally, and this is a minor issue, but there's something wrong with the design of the entry field for the two-factor code. You have to touch to start entering the code -- it is not focused by default -- and you can accidentally touch the second of the six boxes. It should be a single field, not six fields designed to appear as a single six-digit field.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I hope these suggestions are helpful!&lt;/P&gt;</description>
      <pubDate>Wed, 15 Apr 2020 14:14:27 GMT</pubDate>
      <guid>https://community.arlo.com/t5/Arlo/Two-Factor-Authentication-Issues/m-p/1766400#M75296</guid>
      <dc:creator>xaprb</dc:creator>
      <dc:date>2020-04-15T14:14:27Z</dc:date>
    </item>
    <item>
      <title>Re: Two-Factor Authentication Issues</title>
      <link>https://community.arlo.com/t5/Arlo/Two-Factor-Authentication-Issues/m-p/1766602#M75317</link>
      <description>&lt;P&gt;Hi xaprb,&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;We appreciate your feedback. The suggestions made here are noted and will be passed along&amp;nbsp;to the development team.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Apr 2020 16:05:36 GMT</pubDate>
      <guid>https://community.arlo.com/t5/Arlo/Two-Factor-Authentication-Issues/m-p/1766602#M75317</guid>
      <dc:creator>JessicaP</dc:creator>
      <dc:date>2020-04-16T16:05:36Z</dc:date>
    </item>
    <item>
      <title>Re: Two-Factor Authentication Issues</title>
      <link>https://community.arlo.com/t5/Arlo/Two-Factor-Authentication-Issues/m-p/1778969#M76335</link>
      <description>&lt;P&gt;I have the same problem.&amp;nbsp; Did anyone at Arlo do some basic testing???????&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The app is unusable as the original poster said.&amp;nbsp; You go to this infinite loop.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1. Login to app&lt;/P&gt;
&lt;P&gt;2. Arlo app said go check the code sent via SMS&lt;/P&gt;
&lt;P&gt;3. Go to your SMS app&lt;/P&gt;
&lt;P&gt;4. Arlo said login again&lt;/P&gt;
&lt;P&gt;5. Arlo app said go check the code&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is a major issue.&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jun 2020 15:51:49 GMT</pubDate>
      <guid>https://community.arlo.com/t5/Arlo/Two-Factor-Authentication-Issues/m-p/1778969#M76335</guid>
      <dc:creator>tr29</dc:creator>
      <dc:date>2020-06-19T15:51:49Z</dc:date>
    </item>
  </channel>
</rss>

