[
https://issues.apache.org/jira/browse/KUDU-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin updated KUDU-1941:
--------------------------------
Resolution: Fixed
Fix Version/s: 1.4.0
Status: Resolved (was: In Review)
The fix is submitted with 87ddf0ae2584f2394bb26d36c01c16e6719659db
> Server should refuse to start if authentication is 'required' but no auth
> method is configured
> ----------------------------------------------------------------------------------------------
>
> Key: KUDU-1941
> URL: https://issues.apache.org/jira/browse/KUDU-1941
> Project: Kudu
> Issue Type: Bug
> Components: rpc, security
> Affects Versions: 1.3.0
> Reporter: Todd Lipcon
> Assignee: Alexey Serbin
> Labels: usability
> Fix For: 1.4.0
>
>
> I started a server with --rpc_authentication=required, but didn't specify a
> keytab. The server started, but when I try to connect to it, the server
> abruptly disconnects the client (so the client gets a network error and
> retries). The server spews the log:
> {code}
> 0316 08:16:36.271464 (+ 39us) negotiation.cc:281] Negotiation complete:
> Invalid argument: Server connection negotiation failed: server connection
> from 127.0.0.1:55920: RPC authentication (--rpc_authentication) may not be
> required unless Kerberos (--keytab_file) or external PKI
> (--rpc_certificate_file et al) are configured
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
