Hi,
We are deploying Eclipse Che in an environment where applications must be exposed under a shared-host path prefix.
Desired Che URL:
https://example.com/platform/che
During testing, we found that after login, Che generates and controls root-level routes such as:
/oauth/callback/dashboard//api/plugin-registry
For example, the OIDC flow redirects to https://example.com/oauth/callback instead of our desired base path.
- Is hosting the full Che control plane under a path prefix (e.g.,
/platform/che) officially supported?
- Is there a supported way to configure a global base path for the dashboard, oauth callback, api, and plugin registry?
Thank you.
Hi,
We are deploying Eclipse Che in an environment where applications must be exposed under a shared-host path prefix.
Desired Che URL:
https://example.com/platform/cheDuring testing, we found that after login, Che generates and controls root-level routes such as:
/oauth/callback/dashboard//api/plugin-registryFor example, the OIDC flow redirects to
https://example.com/oauth/callbackinstead of our desired base path./platform/che) officially supported?Thank you.