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

Swagger is not acessible for Che without oauth #18156

Closed
4 of 22 tasks
Katka92 opened this issue Oct 21, 2020 · 3 comments
Closed
4 of 22 tasks

Swagger is not acessible for Che without oauth #18156

Katka92 opened this issue Oct 21, 2020 · 3 comments
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator 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.
Milestone

Comments

@Katka92
Copy link
Contributor

Katka92 commented Oct 21, 2020

Describe the bug

I've deployed Che without OAuth and I'm not able to access the swagger page. I see the page for a while, but after a few seconds, an error screen is shown.

Che version

  • latest
  • nightly
  • other: please specify

Steps to reproduce

  1. Deploy Che using chectl : checlt server:start -n katka-che --installer=operator --platform=openshift
  2. Change the CheCluster yaml - set openShiftoAuth to false
  3. Allow user creation in keycloak
  4. Create new user
  5. Access swagger: /swagger
  6. Wait for a few seconds for the error page to appear

Expected behavior

Swagger should be accessible.

Runtime

  • kubernetes (include output of kubectl version)
  • Openshift (include output of oc version) 4.5
  • minikube (include output of minikube version and kubectl version)
  • minishift (include output of minishift version and oc version)
  • docker-desktop + K8S (include output of docker version and kubectl version)
  • other: (please specify)

Screenshots

Screenshot from 2020-10-21 13-21-12

Installation method

  • chectl
    • provide a full command that was used to deploy Eclipse Che (including the output) checlt server:start -n katka-che --installer=operator --platform=openshift
    • provide an output of chectl version command chectl/0.0.20201021-next.b21f570 linux-x64 node-v12.18.3
  • OperatorHub
  • I don't know

Environment

  • my computer
    • Windows
    • Linux
    • macOS
  • Cloud
    • Amazon
    • Azure
    • GCE
    • other (please specify) OpenStack
  • other: please specify
@Katka92 Katka92 added the kind/bug Outline of a bug - must adhere to the bug report template. label Oct 21, 2020
@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 Oct 21, 2020
@rhopp rhopp added area/che-server severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Oct 22, 2020
@rhopp
Copy link
Contributor

rhopp commented Oct 22, 2020

I've added label "area/wsmaster", because swagger is exposing wsmaster API. If you thinkg some other arrea is more appropriate, please change that. Thanks (I have no idea whose responsibility swagger should be 😄 )

@sleshchenko
Copy link
Member

I believe it's caused by eclipse-che/che-operator#491
@tolusha Could you take a look and add swagger as a trusted redirect URL as well?

@tolusha tolusha added area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator severity/P1 Has a major impact to usage or development of the system. and removed team/deploy severity/P2 Has a minor but important impact to the usage or development of the system. labels Oct 26, 2020
@tolusha
Copy link
Contributor

tolusha commented Oct 26, 2020

@sleshchenko
yes, I confirm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator 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.
Projects
None yet
Development

No branches or pull requests

5 participants