authorization

Asking about this since the NSA recently published guidance advising the public and private sectors to transition to cryptographic algorithms that are no less than sha384 & ec384 (elliptic curves).

While Edwards' Curves are different, its worth noting that prior to this update sha256 & secp256k1 were both on the list of acceptable cryptographic algorithms. My deduction was that 128-bit securit

Every now and then we see users new to OPA missing the fact that /v1/data requires the JSON request body to wrap the input document, ala: {"input": {"x": "y"}}. Unless e.g. default assignment is used, OPA currently returns just an empty response for a request missing the "input" wrapper, i.e. {"x": "y"} ... it's easy to see why this would be, given how people likely have worked on their po

With oso 0.11.1 and Rust client code.

When tracking down policy logic failures using the POLAR_LOG=1 environment variable I will see the logging of the execution of all of my inline queries. The problem is that I have lots of these, but usually I'm not interested in the ones in my core policy files which are fairly static and unchanging, but rather I'm interested in those policy sources that

I've read the docs, and it seems you can pass through knex instances, but I didn't see if it supports SQLite3 - could you clarify please?