access-control

Issue split from hasura/graphql-engine#6951

our pytest output has a pretty low signal:noise ratio, and it's often difficult to understand the cause of a test failure, if there is one. [Example: a 8600-line log for what turned out to be a flaky test that passed on a second run](https://app.circleci.com/pipelines/github/hasura/graphql-engine-mono/10008/workflows/5e17c7

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

Description: Feedback from the Cloud Native Microsurvey has shown that there is a gap in the area of auditing cloud native systems and the use of cloud native technology and security. There are several efforts ongoing that are looking at controls in the group such as the security controls working group, however there is still a gap of widespread knowledge about methodology and techniques of au

Projects needed to be implemented:

• https://github.com/casbin-rs/diesel-adapter
• https://github.com/casbin-rs/sqlx-adapter/
• https://github.com/casbin-rs/actix-casbin-auth
• https://github.com/casbin-rs/actix-casbin

After creating a custom login policy, the active identity providers are still listed from default. Same ist for MFA and 2FA, ...

From the screenshots below, you can see that the new policy is loaded after creation and reset. But only the policy itself and not the identity providers and factors:
![image](https://user-images.githubusercontent.com/9405495/143998582-86d03161-287f-4448-b0e4-feca882

Every now and then happens that the instance fails to boot up and it would be good to have a way how to debug it, AWS just provided it. aws-gate should have support for this.

More https://aws.amazon.com/about-aws/whats-new/2021/03/introducing-ec2-serial-console/

When the server rebuilds the policy index and detects any errors, it only outputs a summary of the errors detected (failed to build index: missing imports=1, duplicate definitions=0, load failures=2). This is for two reasons:

• We expect users to always run cerbos compile to catch any problems before pushing any policy changes live.
• If there are too many errors, reporting them all in th