Edit history

Earlier versions of Add support for SSO on self-hosted instances, newest first.

Current version | Edited by Rex
Changes
- When SSO is configured, add a "Login with {SSO name}" button to the login page, and possibly disable user registration.Removed: ### ChecksRemoved: Removed: - ☑ I searched for existing issues and didn't find a duplicate.Removed:
Show

Add support for SSO on self-hosted instances

Problem

I would like to be able to have Single Sign On integration, like with Authelia, Authentik, etc.

Proposed solution

Add OIDC configuation, either through a config file, admin dashboard, or environment variables for docker usage. Whenever a user logs in through the SSO, and the user has not been created yet, a user is automatically created using the preferred_username claim, optionally pulling in the profile picture as well. One of these should probably happen too, preferably configurably:
  • When SSO is configured, disable the user registration and login that is built-in, and just redirect to the OIDC provider.
  • When SSO is configured, add a "Login with {SSO name}" button to the login page, and possibly disable user registration.
Edited by Rex
Changes
- When SSO is configured, add a "Login with {SSO name}" button to the login page, and possibly disable user registration.Removed: ### Notes (optional)Removed: Removed: _No response_Removed: ### Checks
Show

Add support for SSO on self-hosted instances

Problem

I would like to be able to have Single Sign On integration, like with Authelia, Authentik, etc.

Proposed solution

Add OIDC configuation, either through a config file, admin dashboard, or environment variables for docker usage. Whenever a user logs in through the SSO, and the user has not been created yet, a user is automatically created using the preferred_username claim, optionally pulling in the profile picture as well. One of these should probably happen too, preferably configurably:
  • When SSO is configured, disable the user registration and login that is built-in, and just redirect to the OIDC provider.
  • When SSO is configured, add a "Login with {SSO name}" button to the login page, and possibly disable user registration.

Checks

  • ☑ I searched for existing issues and didn't find a duplicate.
Original by Rex
Show

Add support for SSO on self-hosted instances

Problem

I would like to be able to have Single Sign On integration, like with Authelia, Authentik, etc.

Proposed solution

Add OIDC configuation, either through a config file, admin dashboard, or environment variables for docker usage. Whenever a user logs in through the SSO, and the user has not been created yet, a user is automatically created using the preferred_username claim, optionally pulling in the profile picture as well. One of these should probably happen too, preferably configurably:
  • When SSO is configured, disable the user registration and login that is built-in, and just redirect to the OIDC provider.
  • When SSO is configured, add a "Login with {SSO name}" button to the login page, and possibly disable user registration.

Notes (optional)

No response

Checks

  • ☑ I searched for existing issues and didn't find a duplicate.