[Bug]: Unable to perform Azure AD OIDC or GitHub site authorization, same response regardless (probably me)

TL;DR

For "... Interestingly for both My configuration is almost this (for obvious reasons I've changed the URL and creds):": interestingly for both My configuration is almost this (for obvious reasons I've changed the URL and creds): ``yaml log: level: debug encoding: console authentication: required: true session: domain: [redirect_host] secure: false methods: github: enabled:

... Interestingly for both My configuration is *almost* this (for obvious reasons I've changed the URL and creds):

Steps

1. If Azure AD OIDC or GitHub auth in Flipt returns the same response no matter what you send, check your load balancer or CDN caching: add a cache whitelist or bypass for flipt_* cookies. Cached auth responses cause the mismatch, and whitelisting those cookies fixes login.

When to use

You are seeing this: Issue flipt-io/flipt#2292 (closed, 7 comments): ### Bug Description I've setup two authentication methods, an OIDC configuration via Azure AD and a GitHub Oauth... Use this skill when you run into "[Bug]: Unable to perform Azure AD OIDC or GitHub site authorization, same response regardless (probably me)".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

In gh:flipt-io/flipt#2292 (Flipt), the issue reported was: Issue flipt-io/flipt#2292 (closed, 7 comments): ### Bug Description I've setup two authentication methods, an OIDC configuration via Azure AD and a GitHub Oauth... When I try to auth via either method, it's clear that the auth works, however I always get the response in the callback of... `` {"code":16,"message":"handling OIDC callback: unexpected state parameter","details":[]} ... Interestingly for both My configuration is *almost* this (for obvious reasons I've changed the URL and creds): yaml log: level: debug encoding: console authentication: required: true session: domain: [redirect_host] secure: false methods: github: enabled: The verified resolution from the thread: If Azure AD OIDC or GitHub auth in Flipt returns the same response no matter what you send, check your load balancer or CDN caching: add a cache whitelist or bypass for flipt_*` cookies. Cached auth responses cause the mismatch, and whitelisting those cookies fixes login. Source: mount the host path https at container path //github.com/flipt-io/flipt/issues/2292