Dashboard error when viewing dockerconfigjson secret with "auth" encoded credentials instead of "username" and "password" keys #10813
Labels
kind/bug
QA/dev-automation
Issues that engineers have written automation around so QA doesn't have look at this
Setup
Describe the bug
When attempting to view a dockerconfigjson-type secret whose data contains "auths.SOME-REGISTRY: {auth:base64-encoded-string}" instead of "auths.SOME-REGISTRY: {username:USER,password:PASS}", the client experiences an error page with the last of the following javascript errors from the console:
To Reproduce
Result
When attempting to view the secret in the Rancher UI (by clicking the name; not viewing as YAML or anything), there is a short pause and the user gets a white screen with "Cannot read properties of null (reading 'slice')". The console shows additional "null" errors.
Expected Result
The user should be presented with a screen showing details of the secret, including values if the option to view secret data is enabled.
Screenshots
Additional context
This error does not seem to be present in 2.8.2. However, only the registry url is shown; it does not attempt to decode the "auth" block to extract the username:password string.
The text was updated successfully, but these errors were encountered: