Run analysis with All In One Demo

 
// Turn off Demo mode to execute analysis:
DemoMode = false
 
// Allow Keycloak to not require https:
KeyCloakDemoMode = true
 
// Set UseTESK to true:
UseTESK = true
 
// Set TesAPIUrl to the URL where the TES API executing agent is hosted. e.g Funnel or TES-K:
TesAPIUrl=http://<HostName>:8000/v1/tasks
 
// Output bucket prefix for the TES executing agent to write outputs to, default is s3 bucket prefix:
TesOutputBucketPrefix=s3://
 
 

Submit a TES message

Once Funnel is running and the All In One is up and configured, you can submit a TES payload to the Submission Layer.

Note that the project access to the TRE must first be approved, see project access to TRE guide.

Troubleshooting

1. Keycloak console requires HTTPS

If you encounter issues where the Keycloak console requires HTTPS, you can resolve this by accessing the Docker container directly:

1. Access the Docker exec of Keycloak container:

docker exec -it <keycloak-container-name> bash

2. Navigate to the Keycloak bin directory and configure the realm:

cd /opt/keycloak/bin
./kcadm.sh config credentials --server http://localhost:8080 --realm master --user admin
./kcadm.sh update realms/master -s sslRequired=NONE

3. Enter admin for the password when prompted.

2. KeyCloakDemoMode = true in .env but KeyCloak still requires HTTPS

If you have set KeyCloakDemoMode = true in your .env file but KeyCloak still requires HTTPS when logging in locally into the Submission layer, for example, follow these steps:

1. Access the Keycloak console at http://localhost:8085, using the admin credentials:

Username: admin
Password: admin

2. Navigate to each Realm: DARE-Control, DARE-TRE, DARE-Egress by clicking on the Realm name in the left-hand side.
3. Access Realm settings under Configure section on the left-hand side menu.
4. Choose None from the Require SSL dropdown.
5. Click on the Save button.