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.

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

Azure token configuration does not seem to work from UI, password is asked when the project is cloned #22313

Closed
ibuziuk opened this issue Jun 21, 2023 · 3 comments · Fixed by eclipse-che/che-server#529
Assignees
Labels
area/che-server area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. sprint/next

Comments

@ibuziuk
Copy link
Member

ibuziuk commented Jun 21, 2023

Describe the bug

Azure token configuration does not seem to work from UI, password is asked when the project is cloned from Empty Workspace even when the token is part of the .git-credentials/credentials
image

Che version

7.69@latest

Steps to reproduce

  1. Open Dashboard - User Preferences - Personal Access Tokens
  2. Add a token for Azure
  3. SUCCESS: Token is validated and added
  4. Try creating a workspace based on the private project from Azure
  5. ERROR: project can not be clonned

Expected behavior

It should be possible to clone private Azure repository when the PAT is configured

Runtime

OpenShift

Screenshots

No response

Installation method

OperatorHub

Environment

Amazon

Eclipse Che Logs

No response

Additional context

Additionally, I think we might need to do an update placeholder on UI since for Azure email should be used, not username

image

@ibuziuk ibuziuk added the kind/bug Outline of a bug - must adhere to the bug report template. label Jun 21, 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 Jun 21, 2023
@tolusha
Copy link
Contributor

tolusha commented Jun 22, 2023

I am confused, I've always used username not email for scm-username.
In my cases it is Anatolii Bazko.

screenshot-dev azure com-2023 06 22-16_22_27

@ibuziuk
Copy link
Member Author

ibuziuk commented Jun 22, 2023

Basically, when I tried creating PAT on UD for Azure it never worked for me. If email was used the PAT was added but it was not usable e.g. not possible to clone private projects

@ibuziuk
Copy link
Member Author

ibuziuk commented Jun 23, 2023

actually in the docs there is a note The Git provider username. For azure-devops, the user’s email address.https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.6/html/user_guide/using-credentials-and-configurations-in-workspaces#using-a-git-provider-access-token

@ibuziuk ibuziuk added sprint/next severity/P1 Has a major impact to usage or development of the system. area/che-server area/dashboard and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jun 23, 2023
@vinokurig vinokurig self-assigned this Jun 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/che-server area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. sprint/next
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants