rest_missing_callback_param client_id in access token generation
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 175
- Forks
- 45
- Avg merge
- 17h 8m
- Merged PRs (30d)
- 4
Description
I am using this oauth client https://github.com/lepture/authlib/blob/642dfa3264f0afe94c7f6ac7006007a7fd24fbe6/authlib/integrations/starlette_client/apps.py#L71 is not sending client_id which is required by WP-API Oauth2, the fact you require it, is that accordingly to oauth2 specification and authlib python client I use is wrong ? Or is the other way around ?
Thansk
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Authlib Starlette client reference at authlib/integrations/starlette_client/apps.py#L71 and trace the access-token callback parameters in the WP-API OAuth2 implementation. Compare the required client_id behavior with the OAuth2 specification and determine which side is incorrect; done means the interoperability behavior and its expected parameter handling are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, python
- Domain
- api, authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100