Reauthentication for expired tokens is not handled graciously

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Environment:
      OS:
      node.js / npm versions:
      Additional info:
    • None
    • None
    • Developer Tools

      Problem Statement/Rationale

      With an oidc flow, when a token is expired and needs to be refreshed, we receive AND display a MongoServerError. While the re-authentication takes place, the user has to keep trying until it's done. See recording attached.

      Steps to Reproduce

      We'll need an enterprise server on linux, together with a mock-oidc-provider (providing short-lived tokens). 

      This can be setup with mongodb-runner:

       

      mongodb-runner start  --version=8.2.x-enterprise --oidc='--payload={"groups":["testgroup"],"sub":"test","aud":"resource-server-audience-value"} --expiry=60 --skip-refresh-token' 

       

      • connect to the server with Compass
      • wait until the token expires
      • try to fetch documents
      • follow the re-authentication flow
      • keep trying to press the fetch documents button

      Expected Results{}

      We expect a smooth re-auth experience. We expect the user to see a loading status, until the command can be executed successfully.

      Actual Results

      The action fails, the user is presented with a not-actionable error. They can keep re-trying, until eventually it works. 

            Assignee:
            Unassigned
            Reporter:
            Paula Stachova
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: