Re: FW: some questions: : working on re-authentication

 I would like to change the first exception to


- authentication process can rely on the user or user-agent entering personal identification information such as name, username, password, and email address if the web content consistently supports automatic entry.


(From - authentication process can rely on the user or user-agent entering personal identification information such as name, username, password, and email address if the web content does not block automatic entry.)


Automatic entry of user information can not work because autocomplete and the name is not set . It is not quite blocking the user agent rather they are not supported. 


Also if transcribe follows the dictionary definition we can just clarify what we mean in the understanding section. Is that Ok?

All the best

Lisa Seeman

LinkedIn, Twitter





---- On Thu, 21 Dec 2017 11:31:01 +0200 Alastair Campbell<acampbell@nomensa.com> wrote ---- 

      Forgot to CC list…
   
 
 Hi Lisa,
  
  > 1. Does transcribe include copying. Do we need a definition? Will it bar the capture type craziness
 
   
 If you have to ask that, we probably need a definition. I think a general definition means reading from one place (visually or audibly) and entering it in, so yes it includes copying.
  
  
 
 > 2. You put back in limited the scope to re-authentication? why? If you cannot login how does it help that you can re-authenticate 
  
  Thinking about it, with password managers we probably don’t need to do that. I was thinking about the email provider scenario, where you can’t use an email reset method. However, with a username/password + 2nd factor you should be ok.
   I’ll update the doc.
  
 Cheers,
  
 -Alastair