support ngsi-ld api

[chicco785]

Is your feature request related to a problem? Please describe.

Today we have a rule package only for ngsi-v2. We should have one also for NGSI-LD

Describe the solution you'd like

Create a new rego package for NGSI-LD apis.

Describe alternatives you've considered
N/A

Additional context
N/A

[chicco785]

when implementing support for NGSI-LD , include tests also with scorpio (see #187) by @SURAJKALLOLI

[tarik-kafein]

Hi,

Is there any update on the ngsi-ld rego package?
I am kind of stuck on implementing this.

For the below code what do I need to change to support /ngsi-ld/v1/entities

check_policy { current_path := split(request.resource, "/") current_path[1] == "v1" current_path[2] == "policies" request.action == "POST" parsed_body.resource_type == "entity" control_request = {"user":request.user, "action": "CONTROL", "resource":concat("", ["/v2/entities/",parsed_body.access_to]), "tenant":request.tenant, "service_path":request.service_path} user_permitted(control_request) }

Also there is no /v2/types/ enpoint in ngsi-ld, so how can I change tis to support ngsi-ld?

check_policy { current_path := split(request.resource, "/") current_path[1] == "v1" current_path[2] == "policies" request.action in ["GET", "PUT", "PATCH", "DELETE"] policy_id := current_path[3] e := policies[_][_][_] match_policy_id_or_wildcard(e, policy_id) e.resource_type == "entity_type" control_request = {"user":request.user, "action": "CONTROL", "resource":concat("", ["/v2/types/",e.resource]), "tenant":request.tenant, "service_path":request.service_path} user_permitted(control_request) }

Once I have a working version I can also share it.

Appreciate the help. Thanks.

[Cerfoglg]

Sorry for the late reply @tarik-kafein

Currently no ETA on when we'll implement NGSI-LD support, as other tasks take precedence.

Though regarding how it works in relation to the code you referenced: the rego rules are effectively just checking if the path matches in relation to the policies Anubis has (splitting the URL by the "/" and checking each element, checking if there is a policy that enables reading on a GET request, ...). So for ngsi-ld it is the same principle as the example with v2 we already have, but accounting for the different URL formats. Rego can be a bit tricky to work with in this context, but you were on the right track with it.

We'll keep you informed