ok thanks, I will keep it as-is for now and keep this issue open to see when should we should schedule a proper payload parser/validator

Indeed. That's what we do in swh-search....

Oh yeah, forgot about that, that's why you recommended json-ld expansion instead of compaction to validate / handle the payload ?

In JSON-LD, every key not starting with a @ (including id when working with contexts that map id to @id) can be an array, an object containing at l...

could you please point me to where you found this in the ldn specs ? (issue #2)

ie. if an url in the @context is invalid or unreachable it will raise...

Thanks again @anlambert for your feedback on this, I will keep the auth system as-is for now but I will keep the keycloak solution in mind.

Yes, I wanted to do that in another mr but I wrote a simple structural validator to the payload

You're right, I wrote a validator that matches the specs

Jenkins job swh-coarnotify/gitlab-builds #25 succeeded in 46 sec.See Console Output, Blue Ocean and Coverage Report for more details.

Jenkins job swh-coarnotify/gitlab-builds #23 succeeded in 44 sec.See Console Output, Blue Ocean and Coverage Report for more details.

Jenkins job swh-coarnotify/gitlab-builds #22 failed in 44 sec.See Console Output, Blue Ocean and Coverage Report for more details.