idavollen

I've encountered another issue it seems that nginx also adds extra line breaks on the incoming, long access token. therefore although the newly generated oauth2 access token is still fresh...

@xeioex I've fixed my issue by adding the following: `proxy_request_buffering on;`

@xeioex I didn't explicitly turn it off. However, it works well after I added two lines inside _/_oauth2_send_introspection_request_ ``` proxy_set_header Host localhost:8080; proxy_request_buffering on; ```

@xeioex I've located that it has nothing to do with request_buffering, but it is important to have config line below: `proxy_set_header Host localhost:8080;`

any progress? Can you confirm that the client_secret_jwt is for the time being not supported? The more complicated _private_key_jwt_ is already supported, why is the easier one, _client_secret_jwt_ is not...

any feedback? it has been over 3 weeks. can your team either confirm it's bug and give a plan for fixing it, or deny it as a feature?

@muhlemmer I just browsed through the link mentioned by you to this one : [token_endpoint](https://zitadel.com/docs/apis/openidoauth/endpoints#token_endpoint) that lists 4 types: 1. client_secret_basic 2. client_secret_post 3. none (PKCE) 4. private_key_jwt As you...

My above observation fits well with your source code : https://github.com/zitadel/oidc/blob/main/pkg/oidc/discovery.go#L152-L156 ``` const ( AuthMethodBasic AuthMethod = "client_secret_basic" AuthMethodPost AuthMethod = "client_secret_post" AuthMethodNone AuthMethod = "none" AuthMethodPrivateKeyJWT AuthMethod = "private_key_jwt"...

both private_key_jwt and client_secret_jwt are introduced by https://www.rfc-editor.org/rfc/rfc8414.html. Zitadel/oidc is declared as OpenID certified OIDC implementation. I'm just wondering why this client_secret_jwt recommended by RFC8414 is left out by your...

given that my frontend has hostname as **www.frontend.com** and the target or backend has hostname as **my.internal.io**, and my internal web server has generated some anchor links in html with...