I'm running into the same issue, but with another OIDC provider. As part of the certification for that provider we need to ensure a logout also invalidates the OIDC session. That seems to not be possible because: * Supabase does not log out the underlying OIDC session. I think it should! * Supabase does not provide access to the id token, so we cannot supply this to the OIDC logout via id_token_hint So we seem firmly stuck and unable to get verified by the provider.