Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Azure OAuth token is not refreshed if it has been expired #22051

Closed
tolusha opened this issue Mar 9, 2023 · 0 comments
Closed

Azure OAuth token is not refreshed if it has been expired #22051

tolusha opened this issue Mar 9, 2023 · 0 comments
Assignees
@tolusha
Labels
area/factory/server Server side of factory implementation kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. team/A This team is responsible for the Che Operator and all its operands as well as chectl and Hosted Che
Milestone
7.63

Comments

@tolusha
Copy link
Contributor

tolusha commented Mar 9, 2023

Describe the bug

Azure OAuth token is not refreshed if it has been expired

Che version

next (development version)

Steps to reproduce

  1. Deploy Eclipse Che
  2. Create Azure DevOps service OAuth2 secret
  3. Try to start a workspace
  4. Go to user namespace and update personal access token to make it invalid
  5. Try to start a workspace
  6. Workspace startup failed

Expected behavior

Workspace started successfully

Runtime

OpenShift

Screenshots

No response

Installation method

chectl/next

Environment

Linux

Eclipse Che Logs

No response

Additional context

No response
@tolusha tolusha added the kind/bug Outline of a bug - must adhere to the bug report template. label Mar 9, 2023
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Mar 9, 2023
@tolusha tolusha mentioned this issue Mar 9, 2023
Merged
9 tasks
@dmytro-ndp dmytro-ndp added severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. area/factory/server Server side of factory implementation team/A This team is responsible for the Che Operator and all its operands as well as chectl and Hosted Che and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Mar 9, 2023
@tolusha tolusha mentioned this issue Mar 10, 2023
Merged
9 tasks
@tolusha tolusha closed this as completed Mar 10, 2023
@tolusha tolusha added this to the 7.63 milestone Mar 10, 2023
@tolusha tolusha mentioned this issue Mar 10, 2023
Closed
45 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tolusha tolusha

Labels
area/factory/server Server side of factory implementation kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. team/A This team is responsible for the Che Operator and all its operands as well as chectl and Hosted Che
Projects
None yet
Milestone
7.63
Development

No branches or pull requests
3 participants
@dmytro-ndp @tolusha @che-bot