Portworx Backup UI access

Access the Portworx Backup UI using DNS over HTTPS for 2.5.0

note

Make sure that all the associated pods can resolve the DNS name.

If you are on Portworx Backup version 2.5.0 with a load balancer and self-signed certificates and need to access the user interface from a cluster over HTTPS, perform the following steps:

1. From the command prompt, navigate to the cluster where your Portworx Backup is installed.

2. Edit the keycloak sts:

   kubectl edit sts pxcentral-keycloak -n <backup-installed-namespace> 

3. Append this new key in env section:

     - name: KC_HOSTNAME 
           value: <px-backup-ui-host-name>

4. Set the following key values to true:

     - name: KC_HOSTNAME_STRICT
           value: "true"
     - name: KC_HOSTNAME_STRICT_HTTPS
           value: "true"

Access the Portworx Backup UI over HTTP for 2.5.0

If you are on Portworx Backup version 2.5.0, perform the following steps to access Portworx Backup user interface over HTTP:

1. From the command prompt, navigate to the cluster where your Portworx Backup is installed.

2. Edit the keycloak sts:

   kubectl edit sts pxcentral-keycloak -n <backup-installed-namespace>

3. Append this new key in env section:

     - name: KC_HTTP_ENABLED
           value: `true`

4. Delete the following key in env section:

     - name: KC_PROXY 
           value: edge

Browser settings in Keycloak

If you are on Keycloak version 21.1.1 and above, perform the following steps to resolve Keycloak log out issue after a refresh:

1. Login to Keycloak console as an admin user and navigate to left navigation pane.

2. Click Authentication and then click Browser.

3. Navigate to forms and then choose Alternative from the drop-down.

If you are on Keycloak version 16.1.1 and below, perform the following steps to resolve log out issue after a refresh:

1. Login to Keycloak console as an admin user and navigate to left navigation pane.

2. Click Authentication and then choose Browser drop-down that is below the Authentication tab.

3. Navigate to forms row and select the Alternative option and Keylcoak auto-saves this setting.

Keycloak sts to upgrade from 2.5.0 to 2.5.1

If you have modified keycloak sts settings either for HTTP or HTTPS in Portworx Backup version 2.5.0 to access the user interface, you need to revert those changes after upgrading to 2.5.1 version. The values should be in sync with the following keycloak yaml file after reverting all the changes:

- name: KC_HOSTNAME_STRICT
       value: "false"
     - name: KC_HOSTNAME_STRICT_HTTPS
       value: "false"
     - name: PROXY_ADDRESS_FORWARDING
       value: "true"
     - name: KEYCLOAK_ADMIN
       value: admin
     - name: KEYCLOAK_ADMIN_PASSWORD
       value: admin
     - name: KC_HTTP_RELATIVE_PATH
       value: /auth
     - name: KC_DB
       value: postgres
     - name: KC_DB_URL_HOST
       value: pxcentral-keycloak-postgresql
     - name: KC_DB_URL_PORT
       value: "5432"
     - name: KC_DB_USERNAME
       valueFrom:
         secretKeyRef:
           key: postgresql-username
           name: pxcentral-keycloak-postgresql
     - name: KC_DB_PASSWORD
       valueFrom:
         secretKeyRef:
           key: postgresql-password
           name: pxcentral-keycloak-postgresql
     - name: KC_PROXY
       value: edge

If you choose to be on Portworx Backup version 2.5.0 for some reasons, refer the following topic to configure access to the user interface:

• Access user interface over HTTPS or HTTP