acoustic-carpenter-78188
12/22/2025, 12:11 AMflyte-binary:v1.15.3 (I've also tried v1.16.0-b3)
### Describe the bug
I am using Helm chart for deploying flyte-binary:v1.15.3 (I've also tried v1.16.0-b3). After adding GitLab as external OIDC provider, I get the following error:
{"json":{"src":"handlers.go:91"},"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":"2025-09-04T05:59:54Z"}
{"json":{"src":"handlers.go:91"},"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":"2025-09-04T05:59:57Z"}
{"json":{"src":"cookie_manager.go:192"},"level":"error","msg":"Error generating encrypted id token cookie [SECURE_COOKIE_ERROR] Error creating secure cookie, caused by: securecookie: the value is too long","ts":"2025-09-04T05:59:57Z"}
{"json":{"src":"handlers.go:208"},"level":"error","msg":"Error setting encrypted JWT cookie [SECURE_COOKIE_ERROR] Error creating secure cookie, caused by: securecookie: the value is too long","ts":"2025-09-04T05:59:57Z"}
I thought this was fixed in #3750 ?
### Expected behavior
Be able to sign in with GitLab.
### Additional context to reproduce
Helm chart's auth configuration:
auth:
enabled: true
oidc:
baseUrl: https://gitlab.medius.si
clientId: x
clientSecret: x
internal:
clientSecret: x
clientSecretHash: x
authorizedUris:
- x
flyteClient:
scopes:
- profile
- openid
- email
- read_user
### Screenshots
No response
### Are you sure this issue hasn't been raised already?
• Yes
### Have you read the Code of Conduct?
• Yes
flyteorg/flyteacoustic-carpenter-78188
12/22/2025, 12:11 AM