Skip to content
← Back to activity

Immutable solution version

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

Version 1Sign in to save

Complete solution

Covers this Flipt problem: [Bug]: Unable to perform Azure AD OIDC or GitHub site authorization, same response regardless (probably me).. 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.

The problem

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:

What fixed it

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.

Evidence

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

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_SZE3KIDYpx0e-3oD2e1gow" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">[Bug]: Unable to perform Azure AD OIDC or GitHub site authorization, same response regardless (probably me). <span>— Vectle</span></a>