Django authentication with Fediverse software

Using Django Deployment
1

Django authentication with Fediverse software

I am thinking about hosting:

  1. Fediverse software (e.g. Mastodon, Peertube)
  2. other software (e.g. superset)
  3. my Django web app

Problem

  1. the user may need to signup separately on each software
  2. hard to support users as authentication is separated

Approach

I am thinking the solution should be SSO (single sign-on).

Usually, I use django-allauth for authentication.

Technical questions

For Django + other software (e.g. superset), is OpenID connect the answer?

What about Django + Fediverse software?

Does anyone have experience integrating Django authentication with ActivityPub protocol (http://activitypub.rocks/)?

2

SSO is something completely different than what allauth provides.

To implement an SSO solution, all sites must accept a common token from a single authentication site. For example, we use the CAS protocol as our SSO solution, using django-cas-server as the authentication source, and django-cas-ng as the Django-based client. We have other, Java-based applications that use a Java CAS client as part of that solution as well.

It doesn’t matter which protocol you select, as long as you have an authentication client for every application that you want to use it with. The key idea here is that none of the applications authenticate users themselves. They defer that authentication to the SSO provider, accepting some type of token as proof of authentication.

Regardless of the solution selected, you will find it helpful to at least understand the flows on that protocol page - you’ll find just about every web-based solution to work effectively the same way, even though some of the specific details may differ.

3

Thanks, I’ll go through that, this is new territory for me. Maybe I’ll share after I get it working