Hi team,

We have a customer who has deployed CRW 2 on OCP 4.2

He has a proxy environment and the following issue is seen while he git clones:

Looking for git in: git
Using git 2.18.2 from git
> git rev-parse --show-toplevel
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
> git clone https://github.com/wildfly/quickstart /home/theia/quickstart
Cloning into '/home/theia/quickstart'...
fatal: unable to access 'https://github.com/wildfly/quickstart/': SSL certificate problem: self signed certificate in certificate chain

His proxy requires clients to trust our internal root CA. They still need a method for getting CRW to trust that CA so it can pull content through their proxy, and so that it'll trust certificates signed by their internal CA (such as the HTTPS endpoints for their internal git and Maven repositories).

The following is his concern:

"I'm concerned that the portions of CRW that support Maven builds may also need to follow the configured proxy and trust settings. We pull build artifacts from an internal repository. That repository uses HTTPS, and its certificate is signed by our internal CA. Hence if CodeReady Workspaces doesn't use those trust settings for pulling Maven dependencies, then enabling the git clone itself may not be enough to get us up and running."

We have a very unhappy customer here. His ask is that, did we test CRW 2 with OCP 4.2 in in a proxy env?

He has several other bugs opened w.r.t OCP 4 and proxy and all of them have been hanging around for quite some time.

It seems that this should work, but it isn't.

If any more data is required then please ask me here, I will get that arranged.

Thanks,
Fatima