Not sure about integrity -- I've seen very few if at all installations with integrity option enabled. Regarding privacy -- have you made sure both client and server enabled SASL privacy? Both sides must have consistent RPC settings for them to talk.
On Wed, Nov 28, 2018 at 12:58 AM ZongtianHou <zongtian...@icloud.com.invalid> wrote: > Hi,everyone > I am using a hdfs client API to access a secured hdfs cluster. The > kerberos have been set up successfully. When the configuration of > hadoop.rpc.protection in core-site.xml is set to authentication, it works > well. However, when it is set to integration or privacy, the namenode can > not be connected, and the log of namenode give the following error. Does > anyone know what the info mean and what lib is needed for connection in > integration and privacy mode? Any hint will be very appreciated!! > > 2018-11-27 17:14:05,270 WARN SecurityLogger.org.apache.hadoop.ipc.Server: > Auth failed for 127.0.0.1:50769:null (Problem with callback handler) > 2018-11-27 17:14:05,270 INFO org.apache.hadoop.ipc.Server: Socket Reader > #1 for port 8020: readAndProcess from client 127.0.0.1 threw exception > [javax.security.sasl.SaslException: Problem with callback handler [Caused > by javax.security.sasl.SaslException: Client selected unsupported > protection: 1]] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org > >
