* Read cliend_id from keycloak settings
* Authenticate on RH Che 6 server by using offline token
* Set offline token to be specific for test user
Signed-off-by: Dmytro Nochevnov <dnochevnov@codenvy.com>
* Avoid redundant revoking of github token in selenium tests
* Fix clean up after github-related tests execution; remove ssh-key of github.com
* Remove test user which has been created by selenium tests launcher
* Move --multiuser parameter from selenium-test.sh to webdriver.sh
* Compare selenium testing results with multiuser CI job
* Differ 'CI job' from 'build' in terms of comparasion of test results
* Add an ability to set exact number of rerun of selenium tests
* Handle NotFoundException when ssh-key to remove is absent
* Fix multiple call of beforeInvocation method of SeleniumTestHandler
* Extract code to upload ssh-key into github.com in tests
* Don't run CheOneThreadTestsSuite.xml in unstable test execution
* Move hook to the constructor of SeleniumTestHandler
* Add html dumps into the selenium tests report
* Remove useless code from rerun function of webdriver.sh
* Rewrite AddSshKeyForGitHubTest to not duplicate other tests
Multi-user Eclipse Che (#6441)
#### How to run it.
```docker run -it -e CHE_MULTIUSER=true -e CHE_HOST=<your ip> -e CHE_KEYCLOAK_AUTH-SERVER-URL=http://<your ip>:5050/auth -v /var/run/docker.sock:/var/run/docker.sock -v ~/.che-multiuser:/data eclipse/che:nightly start --skip:pull --skip:nightly```
#### How to manage it
- Keycloak configured with two realms. ```Master``` and ```che```. Also we have one user admin/admin in both realm. Admin user in master realm is - super admin.
- Eclipse Che configured for che realm
- We enabled user registration in ```Che``` realm
#### Known limitation
- swagger would not work. We need to upgrade a version. to support openid authentification https://github.com/eclipse/che/issues/6015
- It's working on local docker. We are going to provide scalable version based on OpenShift on next versions.
- Invitation of non-existent users to Eclipse Che organization https://github.com/eclipse/che/issues/6335
#### How to run it when it is in a branch
To run an multiuser Che version, the following steps are required after building the branch:
- Rebuild init, cli and che images (in the given sequence). To do that, proceed to folder _dockerfiles/<image_name>_ and run _build.sh_
- Run Che in a usual way using cli, with additional parameters: `-e CHE_MULTIUSER=true` and `--skip:pull --skip:nightly`
Full command example:
`docker run -it --rm -v /var/run/docker.sock:/var/run/docker.sock -v /home/user/.che:/data -e CHE_MULTIUSER=true eclipse/che-cli:nightly start --skip:pull --skip:nightly`
- MacOS users may need to edit _che.env_ file in the data folder, changing `CHE_HOST` and `CHE_KEYCLOAK_AUTH__SERVER__URL` values to their specific IP.
When start is succeeded, the following docker containers should be created:
- che, exposing 8080 port;
- che_keycloak, exposing 5050 port;
- che_postgres, exposing 5432 port;
Add option --port=<che port> to webdriver.sj script to run tests against
Che deployed in Minishift.
Signed-off-by: Oleksandr Garagatyi <ogaragat@redhat.com>
Moved all the code from script main body to its functions to simplify it.
Add set -e directive to prevent ignorance of possible bugs.
Signed-off-by: Oleksandr Garagatyi <ogaragat@redhat.com>
Dmytro Nochevnov