Mario Enrico Ragucci
12/12/2025, 7:47 PMAsk Inkeep
12/12/2025, 7:47 PMpermit support automation2
12/12/2025, 7:47 PMAsk Inkeep
12/12/2025, 7:47 PMhttp.send within Permit.io's integrated OPA/PDP setup.
OPA itself supports restricting built-in functions through its configuration (using the capabilities setting) , but I couldn't find documentation on how this is exposed or configurable in the Permit.io PDP specifically.
Check out these potentially useful sources:
⢠FAQ | OPAL
⢠Authorization with Open Policy Agent (OPA)
⢠Best Practices for Microservice Authorization
Would you like me to try to answer generally based on OPA's standard configuration options?
*
To help our engineers investigate this further, could you please share:
1. Which Workspace / Project / Env you are using
2. What calls you are performing (as SDK code or CURL)
3. Which PDP version you are running
4. Any relevant logs from your PDPAsk Inkeep
12/12/2025, 7:47 PMNatalia Edelson
12/12/2025, 8:00 PMDan
12/15/2025, 12:53 PMAsk Inkeep
12/15/2025, 12:53 PMAsk Inkeep
12/15/2025, 12:53 PMOpaServerOptions pydantic model encoded as a JSON string. (2)
ā*Option 2: Run OPA Standalone*ā
If you need a custom OPA build with specific capabilities disabled, you can run OPA separately from OPAL Client and configure OPAL to manage it externally using:
export OPAL_POLICY_STORE_URL=<https://opa.billing.yourdomain.com:8181>
(3)
This tells OPAL Client where to find your standalone OPA instance.
You can also set OPAL_INLINE_OPA_ENABLED=False to disable OPAL from running OPA internally. (1)
ā*Option 3: Custom OPAL Client Image*ā
As mentioned, you can build a custom image based on the offAsk Inkeep
12/15/2025, 12:53 PM