Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce "service account" or user group concept #523

Open
soxofaan opened this issue Dec 1, 2023 · 1 comment
Open

Introduce "service account" or user group concept #523

soxofaan opened this issue Dec 1, 2023 · 1 comment

Comments

@soxofaan
Copy link
Member

soxofaan commented Dec 1, 2023

This comes out of discussions about "machine-to-machine" auth, like https://github.com/openEOPlatform/architecture-docs/issues/134 . The question/request is still a bit vague to be honest, but I just wanted to plant a seed here.

The openeo API currently has a user concept, and because of how OIDC works (the recommended auth mechanism in openEO) this pretty much corresponds 1-on-1 to a real person that interacts with a computer or other device.

Often in use cases however we see the need for a less strict "user" definition, for example:

  • (as discussed before) automated, "machine-to-machine" workflows
  • multiple persons acting "interchangeably" in a group on the same project

As noted before, this might be primarily an authentication problem that has to be solved on the level of OIDC.
Still, I'm wondering if there are some places in the openEO API where we might want to eliminate or avoid implicit "user==real person" assumptions.

@m-mohr
Copy link
Member

m-mohr commented Jun 19, 2024

Can you point me to where the openEO API assume a real person? I don't see specific action items to work on right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants