Łukasz Kamiński

Currently, we're forcing users to create policies that always say `allow` and `reason`. There should be a way, to let them interpret and allow/deny access based on their fields.

There should be a way to decorate/substitute default request template with user's own. User might want to send additional information or pre-processed information (like extracted JWT) to OPA so they...

Enable filtering with HTTP properties configured through yaml

8

Currently, we're always using path, method and JWT to make queries to OPA. We should allow for better elasticity.

There should be a way to easily say what should be sent to OPA in a request. The idea is to have annotations that could look like this: ```java @OpaRequest(document...

There has been a discussion over the way of managing dependencies in our project. Currently, we have a `kt` file with dependencies and their versions, so that declaration of dependency...