The UI does not surface any error or failure state when attempting to install and configure the Vulnerability Scanner using invalid credentials. Instead, the installation process appears to hang indefinitely on the final step, leaving the user without guidance on what went wrong.
Steps to reproduce
While running the security-ui-exts development build for a freshly installed instance of Rancher 2.15-head:
- Navigate to Local Cluster Explorer => Vulnerability Scanner and click "Start installation"
- Step 1: Select "Create an HTTP Basic Auth Secret; enter any value for the username; enter any value for the password (testuser/testuser was used for this reproduction); click "Continue"
- Step 2: Click "Add all repositories"
- Step 3: Observe the behavior
Actual behavior
Step 3 is rendered, indefinitely displaying a loading indicator.
Expected behavior
If there is an issue with installing the Vulnerability Scanner, an error message is relayed to the user to indicate what might be wrong.
Additional context
I intentionally entered invalid credentials for this reproduction, but there's a valid scenario where a user might make a typo when initially installing the extension, leaving them in a scenario that's difficult to understand and with unclear recovery steps.
Screenshots

The UI does not surface any error or failure state when attempting to install and configure the Vulnerability Scanner using invalid credentials. Instead, the installation process appears to hang indefinitely on the final step, leaving the user without guidance on what went wrong.
Steps to reproduce
While running the
security-ui-extsdevelopment build for a freshly installed instance of Rancher 2.15-head:Actual behavior
Step 3 is rendered, indefinitely displaying a loading indicator.
Expected behavior
If there is an issue with installing the Vulnerability Scanner, an error message is relayed to the user to indicate what might be wrong.
Additional context
I intentionally entered invalid credentials for this reproduction, but there's a valid scenario where a user might make a typo when initially installing the extension, leaving them in a scenario that's difficult to understand and with unclear recovery steps.
Screenshots