Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • funkwhale funkwhale
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 405
    • Issues 405
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 18
    • Merge requests 18
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • funkwhalefunkwhale
  • funkwhalefunkwhale
  • Issues
  • #1944
Closed
Open
Issue created Nov 05, 2022 by Georg Krause@georgkrauseOwner

Django OAuth Toolkit v2

Django OAuth Toolkit is available in version 2 and we need to update. Sadly its breaking a few features we are using and we need to do this later and deprecate the features now.

At least oob support is dropped, which is a problem for all of our headless clients and eventually third party clients as well. In order to fix this, we should implement Client Authentication Flow, which enables headless clients to consume our APIs and is already supported by django-oauth-toolkit. At the same time we can deprecate OOB and remove it later, which allows us to update the Django OAuth Toolkit.

Assignee
Assign to
Time tracking