Creating Dynamic Policies
Example of a Rego policy
Last updated
Was this helpful?
Example of a Rego policy
Last updated
Was this helpful?
A simple Rego policy that takes a credential subject as input and verifies the subject DID against a given parameter would look like this:
Please refer to the to exectute the command successfully.
You can save the policy by name, which simplifies its usage in future verifications.
Flags:
-n, --name
: Policy name, must not conflict with existing policies
-D, --description
: Optional policy description
-p, --policy
: Path or URL to policy definition. e.g.: rego file for OPA policy engine
-i, --input
: Input JSON object for rego query, which can be overridden/extended on verification. Can be a JSON string or JSON file
-d, --data-path
: JSON path to the data in the credential which should be verified, default: "$" (whole credential object)
-s, --save-policy
: Downloads and/or saves the policy definition locally, rather than keeping the reference to the original URL
-f, --force
: Override existing policy with that name (static policies cannot be overridden!)
-e, --policy-engine
: Policy engine type, default: OPA. Options, OPA
--vc / --no-vc
: Apply/Don't apply to verifiable credentials (default: apply)
--vp / --no-vp
: Apply/Don't apply to verifiable presentations (default: don't apply)
Please refer to the to exectute the command successfully. Example
Please refer to the to serve the API.