Token exchange using client_secret_post as Token Endpoint Authentication Method

Hello,
There are different methods usable for OIDC for the Token Exchange
Right now, as the method isn't specified, it defaults to using client_secret_basic (credentials sent through the the HTTP Authorization header).

While client_secret_basic is the OIDC specification default, many enterprise-grade Identity Providers (such as Ping Identity) use client_secret_post by default.
This create issues for the use of VaultWarden in my company context.