10c1f5d089
Most HTTP API calls will use the default namespace of the calling token to additionally filter/select the data used for the response if one is not specified by the frontend. The internal permissions/authorize endpoint does not do this (you can ask for permissions from different namespaces in on request). Therefore this PR adds the tokens default namespace in the frontend only to our calls to the authorize endpoint. I tried to do it in a place that made it feel like it's getting added in the backend, i.e. in a place which was least likely to ever require changing or thinking about. Note: We are probably going to change this internal endpoint to also inspect the tokens default namespace on the backend. At which point we can revert this commit/PR. * Add the same support for the tokens default partition |
||
|---|---|---|
| .. | ||
| abilities | ||
| adapters | ||
| components | ||
| controllers | ||
| filter/predicates | ||
| helpers | ||
| mixins | ||
| models | ||
| routes | ||
| search/predicates | ||
| serializers | ||
| services | ||
| sort/comparators | ||
| utils | ||