Does the 'client_secret_post' not support token 'revocation'?

Open
#79 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

Research direction

Reproduce the token-revocation request shown in the issue with client_secret_post and compare it with the working client_secret_basic request. The issue does not name a source file or test, so trace the example server's revocation endpoint and client authentication handling first. Done means a valid client_secret_post request succeeds without invalid_client.

Written by the indexing model from the issue text.

Description

image

image
Hi. I tried with 'client_secret_post', but only an error appears ('invalid_client').
(No changes have been made to the source file.)

but, It works if I try after changing to 'client_secret_basic'. (client_metadata)
image

work request format:
image

Can you make it work in the 'client_secret_post' way?
Maybe I'm trying to do something wrong, but I can't solve it even if I change various ways.

Dominant language
Python
Stars
705
Forks
279
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from authlib/example-oauth2-server

All issues in authlib/example-oauth2-server

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.