-
Notifications
You must be signed in to change notification settings - Fork 4
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
load_result
not working in batch jobs when using OIDC user
#126
Comments
soxofaan
added a commit
that referenced
this issue
Feb 25, 2022
openEO processing in batch jobs needs real user id for `load_result` and UDPs to work properly. Proxy user id is just necessary when submitting the job.
soxofaan
added a commit
that referenced
this issue
Mar 9, 2022
PR #128 follow up: no need to keep proxy user id in batch job itself also be more simple/strict in `argv` handling batch_job.py
soxofaan
added a commit
that referenced
this issue
Mar 9, 2022
PR #128 follow up: no need to keep proxy user id in batch job itself also be more simple/strict in `argv` handling batch_job.py
7 tasks
soxofaan
added a commit
that referenced
this issue
Mar 10, 2022
soxofaan
added a commit
that referenced
this issue
Mar 10, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
originally reported here https://discuss.eodc.eu/t/caching-openeo-results/197/22
using
load_result
fails with something likeafter some digging, I found that the job lookup inside a batch job does not work because the batch job uses the proxyuser as user id while the job registry uses (OIDC based) user id
The text was updated successfully, but these errors were encountered: