hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8251) SecurityUtil.fetchServiceTicket broken after HADOOP-6941
Date Fri, 06 Apr 2012 05:01:19 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-8251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248054#comment-13248054

Todd Lipcon commented on HADOOP-8251:

Hey Devaraj. Sorry, I already committed this, and I don't feel comfortable changing the code
if I can't test it (I don't have ready access to an IBM JDK installation). I think rather
than just fixing this bug, someone should run through the whole security test plan on the
IBM JDK -- perhaps as part of HADOOP-7211?

bq. Seems like the methods are there and with the desired signatures..
bq. Did I miss something?

I was basing it on these docs:
which don't mention krb5util in that package
> SecurityUtil.fetchServiceTicket broken after HADOOP-6941
> --------------------------------------------------------
>                 Key: HADOOP-8251
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8251
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 1.1.0, 2.0.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Blocker
>             Fix For: 1.0.3, 1.1.0, 2.0.0
>         Attachments: hadoop-8251-b1.txt, hadoop-8251.txt
> HADOOP-6941 replaced direct references to some classes with reflective access so as to
support other JDKs. Unfortunately there was a mistake in the name of the Krb5Util class, which
broke fetchServiceTicket. This manifests itself as the inability to run checkpoints or other
krb5-SSL HTTP-based transfers:
> java.lang.ClassNotFoundException: sun.security.jgss.krb5

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message