* Don't bind 'user' role to test user
Signed-off-by: Dmytro Nochevnov <dnochevn@redhat.com>
* Remove role 'user' from keycloak
Signed-off-by: Dmytro Nochevnov <dnochevn@redhat.com>
* Add eclipse/theia-dev image
will be used by developers and by theia image (as builder image)
Change-Id: Ie78cb2d616ef6e5a32ce7c34a25b3adab1f28948
Signed-off-by: Florent Benoit <fbenoit@redhat.com>
- Do not use theia start command on production build (fix 0.3.16 image)
Change-Id: I6a6dcab2af663acdfbe79cc71498548f80920dfc
Signed-off-by: Florent Benoit <fbenoit@codenvy.com>
- Reduce the image size by 1GiB (uncompressed size)
- use production mode of yarn (remove all dev dependencies)
- use yarn global instead of npm global (to dedupe)
- cleanup yum packages
- Remove dugite internal git (use of external git). Also use environment variable to define GIT to use avoiding a git binary search operation at each start of container.
- use of yarn autoclean (providing a definition of files to remove from node_modules)
- remove source maps
- remove verdaccio stuff
- remove electron
- remove npm cache
- remove intermediate java files used by theia/java LSP
- remove modules only used at client side
- remove .git files / typescript source files
Change-Id: Iaacca59a3a001f4ec4311fea3d47362731f5ecbb
Signed-off-by: Florent BENOIT <fbenoit@redhat.com>
then, any /projects/* items will use that parent folder to store dependencies and avoid to use current folder
it will avoid any big I/O operations on the /projects folder
Change-Id: I9fee5963808607b93dcc592456845fb5a3d73e4a
Signed-off-by: Florent BENOIT <fbenoit@redhat.com>
Currently in Che there are still a number of requirements in upstream that are not required by the OIDC specification, so that Che still cannot be used with a number of OIDC compliant providers.
For example, in order to have Che working with the [`node-oidc-provider`](https://github.com/panva/node-oidc-provider), the following changes were necessary:
- Remove the requirement to have the email as a claim in the JWT access
token: this is not required the specification and is not supported by a
number of OIDC providers. Normally, the Id token contains such claims.
So now if the email is not in the JWT token the first time the user connects to Che, ten the email is retrieved from the OIDC provider through its `user-profile` endpoint.
- Explicitely specify the the `openid email profile` scope when requesting the access token. Because OIDC providers, when answering to the `userInfo` endpoint, are expected to return claims that corresponds to the scopes of the access token. So if an access token has the `openid` scope only, the `userinfo` might return no claim at all (according to the specification).
Until now it was working since keycloak allows adding claims to the returned tokens anyway.
- Allow supporting fixed redirect Uris: most OIDC providers support having a list of redirect URIs to come back to after the authorization step. But these authorized Uris don't necessarily support wildcards or prefix. Che doesn't support this currently, and these changes introduce 2 fixed callback HTML pages that redirect to the Dashboard / IDE URL of the final page we want to come back to after authentication. This makes Che compatible with more OIDC providers
We introduced a new boolean property to enable / disable fixed redirect URLs:
`che.keycloak.use_fixed_redirect_urls`
whose default value is `false`
- The previous points required some light changes in the Keycloak Javascript adapter file, that we will submit as a PR to the Keycloak project. I, the meantime the `OIDCKeycloak.js` file is still used, but has been updated to be now based on the `keycloak.js` file of the last `4.5.0-final` Keycloak release. This will make this Keycloak PR easier to get accepted.
Please keep in mind that this version upgrade only impacts the alternate OIDC provider case: when using a real Keycloak server, Che *always uses the `keycloak.js` file provided by the Keycloak server*.
Signed-off-by: David Festal <dfestal@redhat.com>
Dmytro Nochevnov