Verify Oso Cloud Has Received Writes
When debugging authorization issues, it can be helpful to verify that your Oso Cloud environment's centralized authorization data has received the data you expect it to have.
This might be particularly useful if your application has many moving parts before it even reaches your authorization logic, because in those cases it may not be immediately obvious when data has been written to Oso Cloud, which in turn could make it harder to understand your authorization results.
To accomplish this, you can create a webhook that Oso Cloud can call whenever it receives a write; we call this feature Oso Cloud Webhook Integration. Currently, this feature is not self-service, and must be configured by an Oso Engineer, so reach out to us if you are interested.
Limitations
- Ingesting data via Oso Sync will not cause Oso Cloud to send data to the webhook.
- For insert operations, Oso Cloud will not report whether the data was already present or was inserted as a result of applying the operation.
- For delete operations, Oso Cloud will not report the exact set of facts that were deleted as a result of applying the operation.
- Oso Cloud will not indefinitely retry delivery to the webhook, so there is no guarantee of delivery. Due to this limitation, this feature isn't suitable for a compliance/archival use case.
We're working on features to address these use cases. If you'd like to learn more, contact us below.
Talk to us
Do you have questions about debugging authorization flows in your app? If so, schedule a 1x1 with an Oso team member. We're happy to help.