Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • P pleroma-support
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 41
    • Issues 41
    • List
    • Boards
    • Service Desk
    • Milestones
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • PleromaPleroma
  • pleroma-support
  • Issues
  • #52
Closed
Open
Issue created Dec 24, 2020 by Michael Collins@mjc1

Possible to use Pleroma as an OAUTH provider to Prosody?

Hey guys.

I know I've asked this before I think in IRC but I can't remember what the issue was.

Is it possible to use Pleroma as an OAUTH provider to allow Pleroma users to authenticate to Prosody (or any other application that supports OAUTH) via Pleroma?

So every Pleroma user would automatically be able to authenticate to Prosody with their Pleroma username and password?

The configuration for Prosody is as follows (for authenticating against Github as an example):

oauth_client_id = "13f8e9cc8928b3409822"
oauth_client_secret = "983161fd3ah608ea7ef35382668aad1927463978"
oauth_url = "https://api.github.com/applications/{{oauth_client_id}}/tokens/{{password}}";

Is there a way of obtaining the oauth_client_id and oauth_client_secret from within the Pleroma application?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking