WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Duo 2-factor authentication and DNS browser extension interaction


From: Lucy Greco
Date: Oct 26, 2017 3:00PM

i am using dragon 15 and i do not have this problem with duow but i do
have a problem with keeping a google docs or any google sweets app open.
if the dns extenchion is running i will get a unable to load document
when ever i change tabs or if i use any of the apps menus this is
driving me nuts because google says its out of scope for them to fix it
and dns never answers. i think its time we push back on newonce to get
them to play nicely with others

Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
Follow me on twitter @accessaces

On Thu, Oct 26, 2017 at 12:25 PM, Martina Svyantek < <EMAIL REMOVED> > wrote:

> Good afternoon.
> I've recently come across an issue with the Dragon Naturally Speaking
> browser extension (such as for Chrome) "breaking" the Duo 2-factor
> authentication process used to sign in to different resources.
> We've been able to replicate this using Windows 7, 8, and 10. This occurs
> with both Dragon Naturally Speaking 13 and 12.5; the browser extension
> doesn't need to even be working correctly with DNS, just enabled on the
> browser itself. Dragon's extension/add-in in Chrome/Firefox/IE appears to
> somehow interfere with 2-factor authentication. If you disable these
> add-ins, you can get past the 2-factor authentication, but then the
> software is turned off. This is the error message when running through Duo
> with the DNS extension enabled:
> Oops!
> You did something we can't handle. Common causes:
> * Using the back button. That's just not supported, sorry.
> * Bookmarking this site. Please bookmark the service you're trying to get
> to instead.
> * You lingered too long here without clicking anything and your session
> expired.
> Click the button below to go back to the application that sent you here.
> The only "solution" that I have encountered is to disable the browser
> extension. This is even the "official" reply from Duo (
> https://help.duo.com/s/article/3342?language=en_US). I have yet to find
> anything from Nuance that recognizes this issue.
> Has anyone else encountered this issue, and do you have any other
> suggestions on how it could be addressed without having to disable the
> browser extension?
> Thanks in advance,
> --
> *Martina Svyantek*
> > > > >