Hello friends! I'm working on a Proof of Concept...
# spicedb
j
Hello friends! I'm working on a Proof of Concept for using authZed and I have a question regarding caveats that I wasn't able to find an answer to in the API docs. 1. When writing context to a relationship, you need to provide the caveat's name that those variables (context keys) are defined on source: https://authzed.com/docs/spicedb/concepts/caveats#writing-relationships-with-caveats-and-context 2. When checking a permission and providing additional context, you only provide the variables (context keys), and not the caveat name. source: https://authzed.com/docs/spicedb/concepts/caveats#issuing-checks This appears to mean that when checking the database, the caveats variables (context keys) need to be unique globally, right? Because we can't specify the specific caveat in the check permission request. --- Specific example: - Caveat1 and Caveat2 both take in a variable (context key) MyCoolVar In the check permission call, how could it know where MyCoolVar applies?
2 Views