Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-7185

Azure DevOps/Bitbucket.org/GitHub.com users can't enter Dev Spaces if 'CHE_FORCE_REFRESH_PERSONAL_ACCESS_TOKEN' property is enabled

XMLWordPrintable

    • False
    • None
    • False
    • Release Notes
    • Hide
      = Dashboard is not available when using the `CHE_FORCE_REFRESH_PERSONAL_ACCESS_TOKEN` property

      There is a known issue affecting workspaces using Microsoft Azure DevOps/Bitbucket/GitHub git providers in connection with the `CHE_FORCE_REFRESH_PERSONAL_ACCESS_TOKEN` property. Every time you start a workspace, a new personal access token (PAT) is added to the previous PATs which are link:https://issues.redhat.com/browse/CRW-7184[not removed]. When the number of existing PATs exceeds five, you can not run the workspace, and the Dashboard is not available.
      Show
      = Dashboard is not available when using the `CHE_FORCE_REFRESH_PERSONAL_ACCESS_TOKEN` property There is a known issue affecting workspaces using Microsoft Azure DevOps/Bitbucket/GitHub git providers in connection with the `CHE_FORCE_REFRESH_PERSONAL_ACCESS_TOKEN` property. Every time you start a workspace, a new personal access token (PAT) is added to the previous PATs which are link: https://issues.redhat.com/browse/CRW-7184 [not removed]. When the number of existing PATs exceeds five, you can not run the workspace, and the Dashboard is not available.
    • Known Issue
    • Done

      Description of problem:

      This is observed for Azure DevOps/Bitbucket.org/GitHub.com git providers when using 'CHE_FORCE_REFRESH_PERSONAL_ACCESS_TOKEN' property.
      Every start a workspace creates new token, but an old is not removed (there is known issue). When their number exceeds 5, run workspace is fail and more of that an <user>-devspaces becomes unavailable, is not possible go to Dashbord.

      See screenshots:



      Workaround
      N/A

      Prerequisites (if any, like setup, operators/versions):

      • configure OAuth in a git provider

      Steps to Reproduce

      • deploy DS 3.16.0
      • add the property 'CHE_FORCE_REFRESH_PERSONAL_ACCESS_TOKEN' to CheCluster
      • run workspace using factory of a git provider
      • try stop/start workspace more than 5 times

       

      Actual results:

      • workspace does not run
      • Dashbord is not available

      Expected results:

      • workspace should run
      • Dashboard is available

      Reproducibility (Always/Intermittent/Only Once):

      Acceptance criteria: 

       

      Definition of Done:

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

       

       *

        1. ds316-azure-refresh-token-Secrets.png
          205 kB
          Shmaraiev Oleksandr
        2. ds316-refresh-token-5-times-azure-no-run-ws.png
          451 kB
          Shmaraiev Oleksandr
        3. ds316-refresh-token-azure-no-available-user-ns-error-.png
          481 kB
          Shmaraiev Oleksandr
        4. ds316-refresh-token-user-ns-no-available.png
          362 kB
          Shmaraiev Oleksandr

              ivinokur-1 Igor Vinokur
              oshmarai Shmaraiev Oleksandr
              Shmaraiev Oleksandr Shmaraiev Oleksandr
              Jana Vrbkova Jana Vrbkova
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: