Open johanneskastl opened 2 months ago
We made a behavioral change in #1257 to resolve the password reset issue from the Argo CD UI and CLI. As a result, the argocd-example-cluster
secret is now treated as the initial password. We are planning to deprecate argocd-example-cluster
secret so the preferred way to reset the password is as described in the upstream documentation.
We missed documenting this new change in the docs: here. Thanks for bringing this to our attention.
Thanks for the explanation, aligning things between operator and non-operator based installations is a very good idea, to not confuse people finding documentation not fitting their way of installation.
Yes, that is our plan. I will keep this issue open to address the documentation gap.
Hmmm, I cannot reliably change the password upon deployment.
The steps I am currently taking are:
argocd-secret
secret to be presentargocd-XXX-cluster
secret to be presentargocd-secret
secret
argocd-secret
secretargocd-XXX-cluster
secret (for the sake of consistency)I am confused by the operator pod spitting out lots of admin password has changed
lines, even if the password has not changed.
Funny thing is that I somehow got this working manually before, but now all I get is a failed login...
OK, I noticed my mistake. I failed to remove the admin:
from the bcrypt output.
But still I get a invalid session: account password has changed since token issued
error when trying to log in.
Describe the bug Although the argocd-operator pod log mentions the admin password as changed multiple times, the
argocd-secret
secret stayed untouched after modifications to theargocd-example-cluster
secret were made. This led to the authentication failing...Manually patching the
argocd-secret
with a bcrypt hash of the new password worked and I could log in.To Reproduce
Following the docs: https://argocd-operator.readthedocs.io/en/latest/usage/basics/#secrets
Steps to reproduce the behavior:
argocd-example-cluster
and theargocd-secret
secretargocd-secret
secret to contain a new passwordargocd-secret
secret contents are still untouched and on the state before step 3.Expected behavior According to the documentation this should have worked and I should be able to log in.
Information
https://raw.githubusercontent.com/argoproj-labs/argocd-operator/v0.10.1/deploy/catalog_source.yaml
If there are more details you would like to know, feel free to reach out.
Kind Regards Johannes