Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-2013

Long lived auth tokens in Java client

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.3.0
    • Fix Version/s: 1.5.0
    • Component/s: client, java, security
    • Labels:
      None

      Description

      From security.adoc:

      Kudu clients do not automatically request fresh tokens after initial token expiration, so long-lived clients in secure clusters are not supported.

      A process to refresh tokens about to expire would enable the use of long-lived clients with secure clusters.

      NOTE: It's possible to get a new token only when primary user credentials are available. In case if a client is created using imported authenticaion_credentials (i.e. using AsyncKuduClient.importAuthenticationCredentials()), re-acquiring a new token is not possible by design.

        Issue Links

          Activity

          Hide
          tlipcon Todd Lipcon added a comment -

          Alexey's already working on this

          Show
          tlipcon Todd Lipcon added a comment - Alexey's already working on this
          Hide
          aserbin Alexey Serbin added a comment -

          Implemented with 603c1578c78c0377ffafdd9c427ebfd8a206bda3

          Show
          aserbin Alexey Serbin added a comment - Implemented with 603c1578c78c0377ffafdd9c427ebfd8a206bda3

            People

            • Assignee:
              aserbin Alexey Serbin
              Reporter:
              mpercy Mike Percy
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development