Support URLs with basic authentication when resolving a devfile #21998
Labels
area/che-server
area/git/oauth-services
OAuth support to authenticate developers with their GitHub, GitLab, Bitbucket etc...accounts
kind/enhancement
A feature request - must adhere to the feature request template.
new¬eworthy
For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes
severity/P1
Has a major impact to usage or development of the system.
sprint/current
status/release-notes-review-needed
Issues that needs to be reviewed by the doc team for the Release Notes wording
Milestone
Is your enhancement related to a problem? Please describe
There are git services for which Che cannot resolve the Devfile.
A workaround is to use the raw URL to the devfile. For example for azure devops the following public URL worked:
For private repositories a developer could still use the same workaround but in this case he should include the personal access token in the URL. For example:
But the che-server fails to resolve the devfile in this case:
The same URL works fine with
cURL
:Describe the solution you'd like
The che-server should be able to resolve the file.
Additional context
I have also tested with a github.com private repository and the message is different:
The URL used was:
Che-server should resolve the file In this case too but it doesn't work.
The text was updated successfully, but these errors were encountered: