You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When litmus is deployed via the homonymous Helm chart, it is likely that the admin secret is pre-configured, for example via External Secrets.
The feature introduced by this PR makes password reset mandatory for the admin account, which means the external secret must be updated after its first login.
In an ideal situation, when the Helm chart variable existingSecret is set, the admin account should not be asked to reset its password. Other use cases would be non-production environments like sandboxing or test environments where security is not a concern.
Please allow making the aforementioned functionality optional, but defaulting to Enabled.
Thanks in advance.
The text was updated successfully, but these errors were encountered:
Hello @gustavoromerobenitez, I have the same problem because I want to preconfigure the admin password via Gitops. Have you found a workaround?
The only workaround I found was updating the source of the external secret (i.e: gcp secret manager secret) after resetting it via the UI. Seed the initial secret with a dummy value and then set the permanent one after resetting it via the ui. Another alternative is to use a version of Litmus Chaos that predates the PR mentioned above.
When litmus is deployed via the homonymous Helm chart, it is likely that the admin secret is pre-configured, for example via External Secrets.
The feature introduced by this PR makes password reset mandatory for the admin account, which means the external secret must be updated after its first login.
In an ideal situation, when the Helm chart variable
existingSecret
is set, the admin account should not be asked to reset its password. Other use cases would be non-production environments like sandboxing or test environments where security is not a concern.Please allow making the aforementioned functionality optional, but defaulting to Enabled.
Thanks in advance.
The text was updated successfully, but these errors were encountered: