-
Bug
-
Resolution: Won't Do
-
Critical
-
2.15.2.GA
-
False
-
None
-
False
-
-
Not Required
-
- Set up a GitLab private project (TLS protected)
- Attempt to access it from a Workspace
Working to provide a workspace for the following conditions:
- 'private' repo on GitLab
- source is on a branch (not main)
When starting the workspace, the user is prompted 'Do you trust the authors of (GitLab repo)?' Response is 'Yes'. A brief message flashes (too quickly to read), then the workspace opens, but no Project is associated (no source code).
Examining the Theia log shows messages like this:
-----------------------
Promise rejection not handled in one second: Error: Error: Cloning into '/projects/nodejs-web-app2'...
996fatal: unable to access 'https://gitlab.cee.redhat.com/rwagner/node_sample_private/': SSL certificate problem: unable to get local issuer certificate
997, reason: Error: Error: Cloning into '/projects/nodejs-web-app2'...
998fatal: unable to access 'https://gitlab.cee.redhat.com/rwagner/node_sample_private/': SSL certificate problem: unable to get local issuer certificate
999
1000With stack trace: Error: Error: Cloning into '/projects/nodejs-web-app2'...
1001fatal: unable to access 'https://gitlab.cee.redhat.com/rwagner/node_sample_private/': SSL certificate problem: unable to get local issuer certificate
1002
1003at TheiaGitCloneCommand.gitClone (/tmp/theia-unpacked/eclipse_che_workspace_plugin.theia/lib/theia-commands.js:198:19)
1004at processTicksAndRejections (internal/process/task_queues.js:97:5)
----------------------
Examining the /public-certs mount on the Theia container shows the expected certificates are in place (and appear valid when examined):
--------------------
bash-4.4$ pwd
/public-certs
bash-4.4$ ls
ca-bundle.crt custom-certs.RH_CertAuth.pem custom-certs.RH_IT_Rootcert.pem custom-certs.RH_Intermediate.pem
