happy-sunset-85283
07/13/2023, 3:35 PM/callback
redirect back from Google.
Most users (who previously interacted with the deployment) still have access, without problems - they can log out and back in, also in incognito / different browser. It seems to be connected to the specific Google user accounts. These accounts have no issues with any other app using oidc though.
flyteadmin
prints this in the logs for the failed attempts:
{
"json": {},
"level": "error",
"msg": "Failed to retrieve tokens from request, redirecting to login handler. Error: [EMPTY_OAUTH_TOKEN] Failure to retrieve cookie [flyte_idt], caused by: http: named cookie not present",
"ts": "2023-07-13T15:25:13Z"
}
I tried so far:
• clearing cookies for the "broken" users, trying different browser
• restarting all flyte components
Any idea what can be causing this issue? What else can I clear / restart to debug further?tall-lock-23197
average-finland-92144
07/14/2023, 11:40 AMhappy-sunset-85283
07/14/2023, 1:03 PMhappy-sunset-85283
07/14/2023, 1:05 PMhappy-sunset-85283
07/14/2023, 1:06 PMaverage-finland-92144
07/14/2023, 1:52 PM$HOME/.flyte/config.yaml
logger:
show-source: true
level: 6
but not sure about the effect on flyteadmin particularlyjolly-whale-9142
08/08/2023, 8:50 AM502
even though they could connect to it and use it before. Do you have any ideas on that one?freezing-airport-6809
jolly-whale-9142
08/10/2023, 2:12 PM2023/08/10 13:36:54 [error] 49#49: *861071 upstream sent too big header while reading response header from upstream, host: "<http://console.flyte.xxx|console.flyte.xxx>", referrer: "<https://console.flyte.xxx/>"
We added proxy-buffer-size: "128k"
to the configmap of that deployment and it seems to have solved the problem.
cc @thankful-tailor-28399 for figuring this outaverage-finland-92144
08/10/2023, 3:27 PM