3 Commits (docs-project-resource)

Author	SHA1	Message	Date
Jeff Mitchell	e8325a9f59	Don't rely on token for scopes collection actions (#210) ... Don't rely on token for scopes collection actions This requires `scope_id` to be passed (via query param) for actions on the scopes collection; that is, listing or creating. However, it removes the dependency on using the token for the scope of the command. For actions on a specific scope, we use the given ID to determine the scope we should be operating at, doing a lookup if necessary. Existing tests have been updated. Of particular note, the CORS test was already operating on the scopes collection so served as a good test to ensure that from an API level the scope_id parameter was being parsed and passed through (the tests fail without adding that query parameter in).	6 years ago
Jeff Mitchell	388a13b10d	Convert scopes to the new paradigm (#206)	6 years ago
Jeff Mitchell	1a1d3058c9	Move verification to a shared package (#197) ... * Move verification to a shared package The verifier is constructed at HTTP request time and added to the context. It can then be called from appropriate handlers with standardized error handling after all the routing. I intentionally did not add to the handlers yet as I am a good distance into the scope updates and didn't want to cause even more merge conflicts. So at the moment authz is again disabled, but once the scope updates are done, this will be integrated back in.	6 years ago