Our great sponsors
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
In the policy file approach, sometimes referred to as policy-as-code, an application's access policies are represented in a standardized notation and stored in a structured file format (yaml, json, a custom format). The application can then read files of this format and make authorization decisions at runtime based on the defined policies. More modern implementations of this approach (like Casbin or OPA) have implemented a custom file format which supports lightweight code blocks that can be executed at runtime to make attribute-based authorization decisions (ex: user has access until 9PM, user with IP address X.X.X.X has access, etc).
Related posts
- Build and Push to GAR and Deploy to GKE - End-to-End CI/CD Pipeline
- Rego for beginners: Introduction to Rego
- Everything You Need to Know About the Difference Between OPA's Rego and AWS Cedar
- Evolving Authorization for Our Advertising Platform
-
OPA (Open Policy Agent) VS selefra - a user suggested alternative
2 projects | 20 Mar 2023