Uploaded image for project: 'FlightPath'
  1. FlightPath
  2. FLPATH-2771

Investigate OAuth Token Refresh Implementation for ros-ocp-backend

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None

      The ros-ocp-backend currently supports OAuth 2.0 authentication through Kubernetes TokenReview API but lacks automatic token refresh capabilities. When tokens expire, clients receive 401 Unauthorized responses and must handle token renewal themselves.

      We need to investigate what changes are required to implement proper token refresh handling.

      The current implementation validates each request independently using Kubernetes TokenReview API and can detect expired tokens through error handling but doesn't provide any refresh mechanism.

              jgil@redhat.com Jordi Gil
              gciavarrini@redhat.com Gloria Ciavarrini
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: