Trying it out: Does not access Grafana automatically

[rsuhendro]

Bear with me for another "Trying it out" question: After entering user and password in the SAMLTest's login page (user rick), it redirects to Grafana login page and stops there instead of login into Grafana. I notice that uname is blank.

logger=context userId=0 orgId=0 uname= t=2023-01-05T14:38:31.024938104Z level=info msg="Request Completed" method=GET >>path=/ status=302 remote_addr=127.0.0.1 time_ms=8 duration=8.13263ms size=29 referer= handler=/

What's wrong with my setup? Appreciate any hints.

Hendro

[itzg]

It's probably been a while since I ran that combination, so it's very likely there's something that has changed with how grafana expects the auth proxy configuration.

[satramcs]

After entering user and password in the SAMLTest's login page (user rick), it redirects to Grafana login page stops there instead of login into Grafana.I tried it in windows. logger-grafana.update.checker t=2023-12-07T06:23:13.41040827 level=error msg="Update check failed" error="failed to get latest.json repo from github.com: Get "https://raw.githubusercontent.com/grafana/grafana/main/latest.json": tls: failed to verify certificate: x509: certificate signed by unknown authority" duration=223.7928ms logger=infra.usagestats t=2023-12-07T06:24:34.041376Z level=info msg=”Usage stats are ready to report" logger-context userid=0 orgld=0 uname=t=2023-12-07T06:24:41.5906385Z level=info msg= error=" [auth.unauthorized] cannot authenticate request" remote_addr=::1 traceID= and logger-context userid=0 orgld=0 uname=t=2023-12-07T06:24:41.5908453Z level=info msg="Request Completed" method=GET path=/api/live/ws status=401 remote_addr=:1 time_ms=0 duration=424μs size=102 referer=handler=/api/live/ws Need little help here. @itzg

[itzg]

Sorry other projects and things distracted me form investing the original issue. The example itself might need to be updated for some changes grafana might have needed. @satramcs in your case the certificate error seems like the image itself might be too old with outdated certificate authorities.