* docs: document how to build a custom scopes backend (#452) Add a 'Custom scopes backend' section to advanced topics documenting the BaseScopes interface behind SCOPES_BACKEND_CLASS, with a worked model-based example that stores scopes in the database. Cross-reference it from the SCOPES_BACKEND_CLASS setting. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018FCYxmQAHaFMFw6Ei9rpWg * docs: address review on custom scopes backend (#452) - Clarify that only SCOPES/DEFAULT_SCOPES are backend-driven; READ_SCOPE/ WRITE_SCOPE are still read directly from settings by the read/write permission helpers. - Fix get_all_scopes docstring: it renders scope descriptions; requested scopes are validated against get_available_scopes. - Use oauth2_settings.APPLICATION_MODEL for the ApplicationScope FK so the example works with a swapped application model. - Make the example get_default_scopes return a subset of get_available_scopes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018FCYxmQAHaFMFw6Ei9rpWg * docs: address second review round on custom scopes backend (#452) - Collapse the model example's get_available_scopes to a single query. - Document that the read/write helpers require the backend's get_all_scopes() to expose the READ_SCOPE/WRITE_SCOPE names (else ImproperlyConfigured). - Correct the READ_SCOPE/WRITE_SCOPE settings notes: they are used regardless of SCOPES_BACKEND_CLASS by the read/write permission helpers. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018FCYxmQAHaFMFw6Ei9rpWg * docs: scope the ImproperlyConfigured note to decorator/mixin only (#452) The DRF permission classes (TokenHasReadWriteScope, TokenHasResourceScope) do not validate READ_SCOPE/WRITE_SCOPE against the backend's get_all_scopes() — only rw_protected_resource and ReadWriteScopedResourceMixin raise ImproperlyConfigured. Clarify this in the custom-scopes-backend note and the READ_SCOPE/WRITE_SCOPE settings reference. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018FCYxmQAHaFMFw6Ei9rpWg * docs: distinguish get_available_scopes (grantability) from get_all_scopes (#452) A custom backend must expose READ_SCOPE/WRITE_SCOPE from get_available_scopes() for tokens to be grantable (validate_scopes checks get_available_scopes), in addition to get_all_scopes() for the rw_protected_resource / ReadWriteScopedResourceMixin ImproperlyConfigured check. Clarify both the custom-scopes-backend note and the READ_SCOPE/WRITE_SCOPE settings reference. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018FCYxmQAHaFMFw6Ei9rpWg --------- Co-authored-by: Claude <noreply@anthropic.com>

Add documentation for model-based scopes #452

Description

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions