Uploaded image for project: 'Sentry'
  1. Sentry
  2. SENTRY-289

Kerberos based connection from HS2 and Metastore to Sentry service fails

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.4.0
    • Fix Version/s: 1.4.0
    • Component/s: None
    • Labels:

      Description

      Secure connection from HS2 to Sentry service fails with no credential errors.
      The Sentry client started by HS2 or metastore needs to wrapp the transport open as privileged action of the current UGI. This allows the SASL negotiation to access the kerberos ticket for authentication.

        Attachments

        1. SENTRY-289.1.patch
          7 kB
          Prasad Suresh Mujumdar
        2. SENTRY-289.2.patch
          9 kB
          Prasad Suresh Mujumdar
        3. SENTRY-289.3.patch
          9 kB
          Prasad Suresh Mujumdar

          Issue Links

            Activity

              People

              • Assignee:
                prasadm Prasad Suresh Mujumdar
                Reporter:
                prasadm Prasad Suresh Mujumdar
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: