Fabian

@bnfinet if you miss the bug_report, can you tell me, where the output is located on windows (do.sh window automatically closed). That's the reason, why I uploaded and obfuscated the...

@bnfinet Sorry, I have no linux system. I can't find any log files and can't find a description in the readme, which logs you need. But I added the debug...

@bnfinet I also provided the nginx log. It looks like the `id_token_hint` is not provided in the `/logout` request as descriped in #258

I'm not sure if this is the same solution as the #885. #885 is about an automatic reaction to the 403 error. From my point of view, #884 is a...

> I think in the end, this & #885 will require an implementation of `sign-out` logic for each provider right? Right because 885 is a general approach independent of the...

> The OIDC provider should provide your ID Token and add it to the session: > > https://github.com/oauth2-proxy/oauth2-proxy/blob/65016c8da155396ce68f7221d8e10703c89f0342/providers/oidc.go#L60 > > Otherwise you'd get an error. You are somehow getting a...

sorry, for my delay. I was not able to passs the `token id` to a cookie, so I can use it to create a logout request in my front-end.

@NickMeves I think the easiest way is, that the `id_token_hint` is general added to the URL specified by the `rd` parameter or duplicate the `oidc` provider type as a new...

I still don't understand why the static HTML page is relevant for this case. The current problem exists in general when `oauth2-proxy` is used as `nginx auth request module` without...

> Dynamic pages can construct the sign-out rd parameter to a URL include the id_token_hint themselves, so they aren't blocked by this issue if they want an IdP provider signout...