Details

    • Type: Sub-task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.8.0
    • Fix Version/s: None
    • Component/s: security
    • Labels:
      None

      Description

      The process for determining the principal name on a login is convoluted, and can behave differently across JVMs. If it's playing up, it's hard to work out what is up.

      I propose

      1. pull out the code to something accessible by kdiag
      2. have it return the principal, and a string describing the origin of the principal (env var, canonical principal, JVM introspection). This can be logged and validated in KDiag, logged @ debug and used in UGI

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              stevel@apache.org Steve Loughran
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: