#Features osirix md how to#

Change the KHEOPS_ROOT_URL to your domain.In the docker-compose.env file change the following:.Add a volume that will store the Let's Encrypt certificates in order to avoid having Let's Encrypt re-issue certificates every time the container is run. When using the Let's Encrypt enabled version of the reverse proxy, the KHEOPS_ROOT_URL environment variable must be a URL accessible from the general internet, and the LETS_ENCRYPT_EMAIL environment variable must be set to the email with which the domain will be registered. To use it, replace the -insecure portion of the tag on the kheops-reverse-proxy with -letsencrypt. Using Let's EncryptДЄ Let's Encrypt enabled reverse proxy for KHEOPS is available. Keycloak must be configured to work using a secured TLS (https) connection in order to secure user credentials. KHEOPS specific Keycloak configuration steps are described here.

#Features osirix md how to#

Please refer to the Keycloak documentation for instruction on how to properly secure Keycloak. KHEOPS interacts with Keycloak using the Authorization Code flow. In a production environment, Keycloak should be set up on a separate domain. Chrome respects the standards and considers connections to 127.0.0.1 to be secure so this issue does not occur. Also on MacOS, Safari does not trust connections to 127.0.0.1, so when loading a study in the OHIF viewer (which is loaded with https), Safari refuses the mixed security connection.On MacOS, the default Docker memory limit of 2GB is not sufficient.

The Register link will be available to create a new KHEOPS account. In order to access Kheops, you will need to register a new account. When you first connect to KHEOPS, you will be redirected to the Keycloak login screen. Once installed, Keycloak will be available at , This script will create a new directory named kheops in which it will download docker-compose configuration files, a keycloak realm configuration, and generate the necessary secrets.