Open-EO / Open-EO/openeo-python-driver
User role support
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 8
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 4
Description
follow up of https://github.com/Open-EO/openeo-aggregator/issues/64
Now, EGI based user role handling is only done at level of aggregator (very simple permission simple: user that is not enrolled properly will not be able to do authenticated requests).
This system has to be moved to openeo-python-driver/openeo-geopyspark-driver, with some things in mind:
- generalize to not only handle the current EGI user role system from openEO platform but also other role/permission systems
- fine-grained permissions on level of collections, processes, job resources, credits, ...?
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 reviewing the linked follow-up issue and the current role handling in the aggregator. The proposed work spans openeo-python-driver and openeo-geopyspark-driver, including generalizing EGI-based roles and defining fine-grained permissions for collections, processes, job resources, and credits. Done would require an agreed design and implementation across these areas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authorization, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100