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

Authentication flow doesn't work #18791

Closed
5 of 22 tasks
vinokurig opened this issue Jan 13, 2021 · 10 comments
Closed
5 of 22 tasks

Authentication flow doesn't work #18791

vinokurig opened this issue Jan 13, 2021 · 10 comments
Assignees
Labels
area/che-server area/install Issues related to installation, including offline/air gap and initial setup 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

@vinokurig
Copy link
Contributor

vinokurig commented Jan 13, 2021

Describe the bug

Authentication popup cant reach the keycloak API.

Che version

  • latest
  • nightly
  • other: please specify

Steps to reproduce

  1. In the dashboard create a workspace.
  2. Go to the projects tab and click Add Project button.
  3. Chose GitHub and click the Connect your GitHub account button.

See: A popup with unavailable address is shown:
Screenshot from 2021-01-13 12-02-57

Expected behavior

The popup should open the redirected url from keycloak.

Runtime

  • kubernetes (include output of kubectl version)
  • Openshift (include output of oc version)
  • 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

Installation method

  • chectl
    • provide a full command that was used to deploy Eclipse Che (including the output)
    • provide an output of chectl version command
  • OperatorHub
  • I don't know

Environment

  • my computer
    • Windows
    • Linux
    • macOS
  • Cloud
    • Amazon
    • Azure
    • GCE
    • other (please specify)
  • other: please specify

Eclipse Che Logs

Additional context

@vinokurig vinokurig added the kind/bug Outline of a bug - must adhere to the bug report template. label Jan 13, 2021
@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 Jan 13, 2021
@benoitf benoitf added area/dashboard and removed area/che-server status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jan 13, 2021
@benoitf
Copy link
Contributor

benoitf commented Jan 13, 2021

@vinokurig as dashboard is switching over to dashboard-next maybe there is no longer this issue (if login is no longer there)
cc @sleshchenko

@benoitf benoitf added the severity/P1 Has a major impact to usage or development of the system. label Jan 13, 2021
@vinokurig
Copy link
Contributor Author

vinokurig commented Jan 13, 2021

@benoitf The issue is not related to dashboard, It can be reproduced from a workspace by signing in GitHub pull-request plugin or other plugins that use GitHub e.g. Git or SSH plugin. I mentioned dashboard as it is the easiest way to reproduce the problem.

@tolusha
Copy link
Contributor

tolusha commented Jan 13, 2021

Everything should work for GitHub PR plugin
eclipse-che/che-theia#953

@tolusha
Copy link
Contributor

tolusha commented Jan 13, 2021

I tend to think it is just a dashboard issue.

@benoitf
Copy link
Contributor

benoitf commented Jan 13, 2021

@vinokurig the flow you're describing in the issue is specific to the dashboard (there is no server code involved)

@sleshchenko
Copy link
Member

as dashboard is switching over to dashboard-next maybe there is no longer this issue (if login is no longer there)

that's true. New Dashboard does not have this functionality yet. This issue will be fixed by our team only in case it's a critical for CRW.

@vinokurig
Copy link
Contributor Author

@benoitf @tolusha

Everything should work for GitHub PR plugin

Actually it doesn't work because the authentication request is called here: https://github.com/eclipse/che/blob/f9d8638acb0d75daf72dae1a38463768df778f54/assembly/assembly-root-war/src/main/webapp/_app/oauthLoader.js#L160-L164

@vinokurig
Copy link
Contributor Author

Even when I do the request manually with the API url from the CHE_API_EXTERNAL env variable:

https://che-che.192.168.99.254.nip.io/api/oauth/authenticate?oauth_provider=github&redirect_after_login=https://che-che.192.168.99.254.nip.io&scope=repo&token=<user token>

it doesn't work.

@vinokurig
Copy link
Contributor Author

@benoitf

@vinokurig the flow you're describing in the issue is specific to the dashboard (there is no server code involved)

The server side is involved because the popup calls the server API which is redirecting to an unavailable url.

@sleshchenko
Copy link
Member

Seems there is nothing Dashboard does with it. Probably it's related to #18225 and somewhere internal URL is used, but publish must be.

@AndrienkoAleksandr AndrienkoAleksandr self-assigned this Jan 14, 2021
@tolusha tolusha added the area/install Issues related to installation, including offline/air gap and initial setup label Jan 14, 2021
@tolusha tolusha modified the milestone: 7.25 Jan 14, 2021
@tolusha tolusha mentioned this issue Jan 15, 2021
54 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/che-server area/install Issues related to installation, including offline/air gap and initial setup 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

6 participants