It can use the policy parameter evaluation functions from the utility module implemented in #16 . Therefore the policy-handling will be similar, but interactions with authorisation registries and JWT token validation and verification will be different.
This should be added as additional authorization mode to role-based (the default) and iSHARE-compliant (implemented here: https://github.com/FIWARE/api-umbrella/blob/master/src/api-umbrella/proxy/middleware/policy_validator_cb_ishare_auto.lua), but will be similar to the iSHARE-compliant one.
It can use the policy parameter evaluation functions from the utility module implemented in #16 . Therefore the policy-handling will be similar, but interactions with authorisation registries and JWT token validation and verification will be different.