[CASSANDRA-5208] cli shouldn't set default username and password

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 1.2.2
• Component/s: Legacy/Tools
• Severity: Low
• Assignee: Aleksey Yeschenko
• Reporter: Aleksey Yeschenko

Authors

Aleksey Yeschenko

Reviewers

Jonathan Ellis

• Created: 31/Jan/13 19:00
• Updated: 16/Apr/19 09:32
• Resolved: 31/Jan/13 19:17

Description

Currently cli sets default username and password if none are set (in CliOptions.processArgs). Because of this cli will always authenticate, whether or not this was the intent of the user and CliMain.connect() "if ((sessionState.username != null) && (sessionState.password != null))" condition will always be true.

This breaks authentication in at least two scenarios:
1. Authenticator allows anonymous access and a user wants to login anonymously - instead he will get AuthenticationException because user "default" will most likely not exist.
2. Authenticator doesn't user username/password pairs for login but something like Kerberos instead. Thrift's login with u:default, p:"" will still be called and AuthenticationException will be thrown, again.