-
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
Support single-host mode on the multi-user server #14335
Conversation
…ends changes in the che-jwtproxy component. * Add a distinction between service name and path base in the external server exposer to be able to correctly expose a service through a proxy * the async authentication in loader.js doesn't truncate the path anymore so that it can correctly locate /jwt/auth even in single-host mode * enhance the jwt proxy configuration with the ability use custom uri prefixes for the redirects on auth failure - this can be used to pass in the information about the external path the proxy is available on even if hidden behind a path rewriting ingress Signed-off-by: Lukas Krejci <lkrejci@redhat.com>
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:
|
Signed-off-by: Lukas Krejci <lkrejci@redhat.com>
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
...se/che/workspace/infrastructure/kubernetes/server/secure/jwtproxy/JwtProxyConfigBuilder.java
Show resolved
Hide resolved
ci-test |
crw-ci-test |
...ipse/che/workspace/infrastructure/kubernetes/server/secure/jwtproxy/JwtProxyProvisioner.java
Outdated
Show resolved
Hide resolved
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
@metlos : about failed deployment of Che here in test results:
|
Thanks for investigating @SkorikSergey. That is rather weird, I'll take a look. |
the auth request. Signed-off-by: Lukas Krejci <lkrejci@redhat.com>
* provided overriden bindings for OpenShift infra * Renamed IngressServiceExposureStrategy to ExternalServiceExposureStrategy so that it is not confusing on OpenShift where ingresses are not used * Made the cookie path server-strategy sensitive Signed-off-by: Lukas Krejci <lkrejci@redhat.com>
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
ci-test |
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
ci-test |
ci-test |
crw-ci-test |
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:
|
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
ci-test |
assembly/assembly-wsmaster-war/src/main/webapp/WEB-INF/classes/che/che.properties
Outdated
Show resolved
Hide resolved
ci-test |
…-user Signed-off-by: Lukas Krejci <lkrejci@redhat.com>
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
Signed-off-by: Lukas Krejci <lkrejci@redhat.com>
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
ci-test |
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
Signed-off-by: Lukas Krejci <lkrejci@redhat.com>
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:
|
…-user Signed-off-by: Lukas Krejci <lkrejci@redhat.com>
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
assembly/assembly-wsmaster-war/src/main/webapp/WEB-INF/classes/che/che.properties
Show resolved
Hide resolved
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has failed:
|
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
@metlos: about this Happy path tests failure - it was changes in upstream Theia project, which affected our tests. |
…-user Signed-off-by: Lukas Krejci <lkrejci@redhat.com>
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E tests of Eclipse Che Multiuser on OCP has been successful:
|
What does this PR do?
server exposer to be able to correctly expose a service through a proxy
anymore so that it can correctly locate /jwt/auth even in single-host mode
prefixes for the redirects on auth failure - this can be used to pass in
the information about the external path the proxy is available on even if
hidden behind a path rewriting ingress
Note that this depends changes in the che-jwtproxy component.
What issues does this PR fix or reference?
#14189
eclipse-che/che-jwtproxy#11