-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Set basic access authentication for registries requests #15292
Conversation
…e registries Signed-off-by: Oleksii Orel <oorel@redhat.com>
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1) ℹ️ |
E2E tests of Eclipse Che Multiuser on OCP has been successful:
|
@olexii4 I wonder why you didn't use keycloak-token-interceptor.ts to fix resolve this issue? |
@akurinnoy In issue #14627 we decide to provide an ability to configure plugin/devfile registries as secure. That is why I added dummy implementation as a first step. Ok. I will change it |
@olexii4 @akurinnoy until we introduce secure registry feature can you just remove any authorization header at all? CC @l0rd |
@skabashnyuk Sure, that was my advise to @olexii4 |
… devfile registries
…gin and devfile registries
@skabashnyuk done |
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1) ℹ️ |
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1) ℹ️ |
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
* set basic access authentication for requests to the plugin and devfile registries Signed-off-by: Oleksii Orel <oorel@redhat.com>
Signed-off-by: Oleksii Orel oorel@redhat.com
What does this PR do?
This PR sets basic access authentication for plugin and devfile registries.
What issues does this PR fix or reference?
#14627