Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • funkwhale funkwhale
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 384
    • Issues 384
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • funkwhale
  • funkwhalefunkwhale
  • Issues
  • #136

Closed
Open
Created Mar 24, 2018 by Agate@agate💬Owner

[federation] subscribe/authorize logic

Note: this meta ticket will probably be splitted in sub tickets.

At first, music catalog federation will be opt-in, meaning instance A will ask instance B to get access to its catalog. Instance B will accept or deny instance A request. In case of accept, a token/key/whatever will be send to instance A to give it access to instance B API and catalog.

To achieve that, we need:

  • A model to store Instances (name, url, first_seen date)
  • A token model (instance, token_value, valid_until, etc.)
  • A federation request model (instance, creation_date, status), with a constraint to ensure we don't have more than one open request per instance
  • A federation setting (probably a preference) to allow instance owner to enable or disable federation requests
  • A federation request endpoint for creating/updating requests
  • The logic to send the token to the accepted instance. In fact, it looks like a private/public key combined with signing HTTP requests is the way to handle this problem, according to https://www.w3.org/wiki/SocialCG/ActivityPub/Authentication_Authorization
  • A front-end view to list/accept/deny federation requests
  • A front-end view to list/revoke federation tokens
Edited Mar 24, 2018 by Agate
Assignee
Assign to
Time tracking