Fuzzball Documentation
Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Back to homepage

Accessing the Web Interface and Authentication

If you’ve followed the previous steps to establish an SSH tunnel and configure your browser to use the SOCKS proxy, you can now access the Fuzzball web UI from your local web browser.

To obtain the URLs for the User UI and Admin UI, along with the login credentials, use the convenience script provided by CIQ. Execute the commands below on the Server node.

$ wget https://ciq-marketplace-assets.s3.us-east-1.amazonaws.com/public/fuzzball/scripts/deployment-info-wait.sh

$ chmod +x deployment-info-wait.sh

$ ./deployment-info-wait.sh
-------------------CLUSTER INFORMATION--------------------

Keycloak URL:     https://auth.10.0.0.99.nip.io/auth/realms/f7c25400-0c57-4002-a457-5f8a70236ae8
Fuzzball API URL: https://api.10.0.0.99.nip.io
Fuzzball UI URL:  https://ui.10.0.0.99.nip.io
Fuzzball Admin UI URL: https://ui-admin.10.0.0.99.nip.io

Fuzzball admin account:
- username: admin@ciq.com
- password: -Pd[Fo(i)&302M=Q

Fuzzball cluster admin account:
- username: fuzzball-admin
- password: zuK>Rxu[]18*4PCi

Keycloak admin account:
- username: keycloak
- password: keycloak

...

The credentials listed under “Fuzzball admin account” are used to access the standard Fuzzball UI, while the “Fuzzball cluster admin account” credentials are required for accessing the Fuzzball Admin UI.

Open your web browser and navigate to the URL provided for the User UI or Admin UI. You will be prompted to log in. Use the credentials provided by the convenience script.

Local fuzzball admin ui login page

Check out the quick start guide for more information on using the Fuzzball web UI.

This simple deployment uses a self-signed certificate. Therefore you will have to give your browser permission to visit the site explicitly when you connect for the first time. In addition you will also have to visit the URL of the Fuzzball API and grant your browser permission to access this site once. If you skip this step you may notice that, for example, logs of workflows are not available. You can determine the URL serving the API with

kubectl get ingress -n fuzzball fuzzball-openapi -o "jsonpath={.spec.rules[].host}"