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

Your session has expired. Please login to Che again to get access to your OpenShift account

    XMLWordPrintable

Details

    • False
    • False
    • Hide
      = Error message asking the user to log in again at workspace startup

      When starting a workspace, users might receive the following error message: *Your session has expired. Please login to Che again to get access to your OpenShift account.*

      .Workaround

      * Log in again.
      Show
      = Error message asking the user to log in again at workspace startup When starting a workspace, users might receive the following error message: *Your session has expired. Please login to Che again to get access to your OpenShift account.* .Workaround * Log in again.

    Description

      Multiple issues reported same problem  during workspace startup

       

       

      Your session has expired. Please login to Che again to get access to your OpenShift account

      https://issues.redhat.com/browse/CRW-1767
      https://issues.redhat.com/browse/CRW-2001

       

       

      Usually, it means that the keycloak token that uses to obtain the Openshift token has been expired. It happens due to wrong exchange algorithm see OpenShift token retrieval from Keycloak may return a stale token https://github.com/eclipse/che/issues/19720 and multiple token transformation see OpenShift token retrieval from Keycloak should happen only once during workspace startup/suspension https://github.com/eclipse/che/issues/19724

       

       

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. CRW-2001 CRW 2.9 is not able to create a project based on any (eg empty) devFile

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. CRW-1767 CRW 2.8.0 workspace startup failure message is misleading when mkdir pod reached timeout

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. CRW-1650 Some API calls are not working when keycloak-owned openshift token expires.

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          links to

          Web Link OpenShift token retrieval from Keycloak may return a stale token

          Web Link OpenShift token retrieval from Keycloak should happen only once during workspace startup/suspension

          Activity

            People

              skabashn Sergii Kabashniuk
              skabashn Sergii Kabashniuk
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: