Closed swapzero closed 8 months ago
Issue is coming from grafana >=10.2.3: https://github.com/grafana/grafana/issues/79753
You can resolve it by downgrading grafana to version 10.2.2
Hi @bruceoutdoors
I wonder if this is something related to LDAP authentication. I have tried to replicate the issue using regular password-based authentication and everything seems to be working fine:
What is the LDAP configuration you are using in the Grafana Operator deployment?
yes it is LDAP related. I’m using jumpcloud.
Also I’m not using grafana operator (I didn’t read where I was earlier haha) - but just thought I mention issue is from upstream.
Thanks so much for bringing up the context @bruceoutdoors ! I missed your link to the upstream project when I first saw your comment 😅 .
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
Name and Version
bitnami/grafana-operator > 3.5.11
What architecture are you using?
amd64
What steps will reproduce the bug?
Are you using any custom parameters or values?
No response
What is the expected behavior?
to see grafana login screen
What do you see instead?
502 Bad Gateway
Additional information
grafana deployed with grafana-operator chart v3.5.11 doesn't have this issue.