I am encountering an error when accessing the OpenIddict server using rapidoc's Authorization Code Flow:
`Multiple client credentials cannot be specified.'
After some investigation, I found out that rapidoc carries the client_id when accessing the Token URL.
Is there a setting for rapidoc to not carry the client_id when accessing the Token URL in the Authorization Code Flow?
Original in Chinese
我在使用 rapidoc 的授权代码流访问 OpenIddict 服务器时遇到了一个错误：
`Multiple client credentials cannot be specified.`
在经过调查后发现是 rapidoc 在访问 Token URL 时携带了 client_id 造成的。
有没有一种设置能够让 rapidoc 在授权代码流中访问 Token URL 时不要携带 client_id？
Why not use 'Request Body'
I am encountering an error when accessing the OpenIddict server using rapidoc's Authorization Code Flow: `Multiple client credentials cannot be specified.'
After some investigation, I found out that rapidoc carries the client_id when accessing the Token URL. Is there a setting for rapidoc to not carry the client_id when accessing the Token URL in the Authorization Code Flow?
Original in Chinese
我在使用 rapidoc 的授权代码流访问 OpenIddict 服务器时遇到了一个错误： `Multiple client credentials cannot be specified.` 在经过调查后发现是 rapidoc 在访问 Token URL 时携带了 client_id 造成的。 有没有一种设置能够让 rapidoc 在授权代码流中访问 Token URL 时不要携带 client_id？Why not use 'Request Body'
