Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-7101

UserGroupInformation.getCurrentUser() fails when called from non-Hadoop JAAS context

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 0.22.0
    • 1.2.0, 0.23.0
    • security
    • None
    • Reviewed

    Description

      If a Hadoop client is run from inside a container like Tomcat, and the current AccessControlContext has a Subject associated with it that is not created by Hadoop, then UserGroupInformation.getCurrentUser() will throw NoSuchElementException, since it assumes that any Subject will have a hadoop User principal.

      Attachments

        1. hadoop-7101.txt
          3 kB
          Todd Lipcon
        2. hadoop-7101.branch-1.patch
          2 kB
          Suresh Srinivas

        Issue Links

          is required by

          Bug - A problem which impairs or prevents the functions of the product. HADOOP-9280 HADOOP-7101 was never merged from 0.23.x to the 1.x branch

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          relates to

          Bug - A problem which impairs or prevents the functions of the product. HADOOP-7070 JAAS configuration should delegate unknown application names to pre-existing configuration

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. HADOOP-8572 Have the ability to force the use of the login user

          • Major - Major loss of function.
          • Open

          Activity

            People

              tlipcon Todd Lipcon
              tlipcon Todd Lipcon
              Votes:
              0 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: