You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2014/02/21 00:41:23 UTC
[jira] [Comment Edited] (HBASE-10527) TestTokenAuthentication fails
with the IBM JDK
[ https://issues.apache.org/jira/browse/HBASE-10527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907711#comment-13907711 ]
Andrew Purtell edited comment on HBASE-10527 at 2/20/14 11:41 PM:
------------------------------------------------------------------
bq. The Oracle JDK implementation of BAOS zero initializes the underlying byte[]. However, IBM JDK does not seem to. This seems to matter in computing the SHA1 for the token identifier password, where the trailing \x00 bytes do not change the SHA1 in the Oracle JDK, but the additional uninitialized junk does change the resulting SHA1 with IBM JDK.
That makes complete sense. All that digging for such a simple fix. Thanks so much Gary, +1
Edit: Fix formatting
was (Author: apurtell):
bq, The Oracle JDK implementation of BAOS zero initializes the underlying byte[]. However, IBM JDK does not seem to. This seems to matter in computing the SHA1 for the token identifier password, where the trailing \x00 bytes do not change the SHA1 in the Oracle JDK, but the additional uninitialized junk does change the resulting SHA1 with IBM JDK.
That makes complete sense. All that digging for such a simple fix. Thanks so much Gary, +1
> TestTokenAuthentication fails with the IBM JDK
> ----------------------------------------------
>
> Key: HBASE-10527
> URL: https://issues.apache.org/jira/browse/HBASE-10527
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.98.0
> Environment: IBM J9 VM (build 2.7, JRE 1.7.0 Linux amd64-64 Compressed References 20131114_175264 (JIT enabled, AOT enabled)
> Reporter: Andrew Purtell
> Assignee: Gary Helmling
> Priority: Minor
> Attachments: HBASE-10527.patch, org.apache.hadoop.hbase.security.token.TestTokenAuthentication-output.txt.gz
>
>
> "DIGEST-MD5: digest response format violation. Mismatched response."
> The failure trace:
> {noformat}
> 2014-02-13 15:41:00,449 WARN [RpcServer.reader=1,port=54751] ipc.RpcServer$Listener(794): RpcServer.listener,port=54751: count of bytes read: 0
> javax.security.sasl.SaslException: DIGEST-MD5: digest response format violation. Mismatched response.
> at com.ibm.security.sasl.digest.DigestMD5Server.validateClientResponse(DigestMD5Server.java:614)
> at com.ibm.security.sasl.digest.DigestMD5Server.evaluateResponse(DigestMD5Server.java:234)
> at org.apache.hadoop.hbase.ipc.RpcServer$Connection.saslReadAndProcess(RpcServer.java:1315)
> at org.apache.hadoop.hbase.ipc.RpcServer$Connection.readAndProcess(RpcServer.java:1501)
> at org.apache.hadoop.hbase.ipc.RpcServer$Listener.doRead(RpcServer.java:790)
> at org.apache.hadoop.hbase.ipc.RpcServer$Listener$Reader.doRunLoop(RpcServer.java:581)
> at org.apache.hadoop.hbase.ipc.RpcServer$Listener$Reader.run(RpcServer.java:556)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1170)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:640)
> at java.lang.Thread.run(Thread.java:853)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)