ctubbsii commented on issue #3495:
URL: https://github.com/apache/accumulo/issues/3495#issuecomment-1601803506

   > I wonder if the endless loop was due to the password being wrong vs not 
being set I wonder if this issue exists in 2.1.0 with an incorrect password set 
and authTimeout occurring
   
   Confirmed that was the case. It seems to me that any time after the first 
failure, whether we're using a client config file or not, it should revert to 
an interactive password prompt. If the credentials are bad in the client config 
file, it's never going to work and you should be prompted, and if it's bad when 
interactively prompted the first time, then the retry is also going to be an 
interactive prompt. So, in both cases after the first attempt, it should retry 
using an interactive prompt.
   
   The message could still be cleaned up in the re-authentication case when 
using the client config file, though. It seems weird to ask the user to 
re-authenticate, only to automatically have it happen for them... at the very 
least, a subsequent message could be shown that says it was done using the 
client config file, so the user doesn't just see a request to re-authenticate, 
followed by no prompt to actually do so.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to