Open-EO / Open-EO/openeo-python-client
Deprecate OIDC Authorization code grant support and usage
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 217
- Forks
- 56
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
The initial OIDC implementation in the openEO python client was focused on the Authorization code grant (the flow that works with redirect urls and such).
Getting this working in a python client context is far from trivial in practice because of the networking aspects of the redirect url.
Now that the Device Authorization Grant (aka device flow) is getting more popular and more widely supported, nobody is probably going to use the Authorization code grant.
Possible action points
- current documentation is currently is quite focused on Authorization Code Grant (in terms of priority and documentation volume). The device auth grant should get more focus instead
- remove implementation parts related to Auth Code Grant, which should make the OIDC implementation easier to maintain
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 by locating the Python client's OIDC implementation and documentation for the Authorization Code Grant, then compare them with the Device Authorization Grant flow. Done means the device flow receives the primary documentation focus and obsolete Authorization Code Grant implementation and usage are removed or deprecated consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication, documentation
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100