-
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
Unable to create workspace from self-hosted gitlab #21555
Comments
@vinokurig could you take a look please |
Could not reproduce the error. I've setup a self hosted gitlab server and the authentication flow worked well. Tipically the |
Gitlab instance works fine, but that's the first application that is connected to the API
Can you help me to narrow down the issue ? Can I add more logs to che server pod ? spec:
server:
customCheProperties:
CHE_LOGGER_CONFIG: "org.eclipse.che.security.oauth.EmbeddedOAuthAPI=DEBUG" Thanks ! |
@a-elie Can you check your |
@a-elie Have you tried to test the flow with the SAAS gitlab? |
So ... it works fine on gitlab.com
I removed user-che namespace on OKD and tried again on self-hosted, same error : |
Thanks for your help, the issue was not with gitlab auth_provider Got some helpful logs with : apiVersion: org.eclipse.che/v2
kind: CheCluster
name: eclipse-che
spec:
components:
cheServer:
debug: true
logLevel: DEBUG |
Describe the bug
"Unexpected end of file from server" on Gitlab OAuth (state=oauth_provider=gitlab)
Che version
7.50@latest
Steps to reproduce
eclipse che
to use your accountExpected behavior
che
pod logs)Runtime
OpenShift
Screenshots
Installation method
OperatorHub
Environment
other (please specify in additional context)
Eclipse Che Logs
Additional context
OpenShift version 4.10.0-0.okd-2022-03-07-131213
Eclipse Che 7.50
GitLab Community Edition 14.9.3
Still doesn't work with a github provider registred (and the warning is gone)
Works fine with github : https://eclipse-che.apps.lab.okd.local/#https://github.com/a-elie/web-app-test
The text was updated successfully, but these errors were encountered: