Skip to main content

Integrate with Fluxer

Support level: Community

What is Fluxer?​

Fluxer is a free and open source chat platform for friends, groups, and communities, with text chat, voice and video calls, screen sharing, and self-hosting.

-- https://fluxer.app/

Preparation​

The following placeholders are used in this guide:

  • fluxer.company is the FQDN of the Fluxer installation.
  • authentik.company is the FQDN of the authentik installation.
info

This documentation lists only the settings that you need to change from their default values. Be aware that any changes other than those explicitly mentioned in this guide could cause issues accessing your application.

authentik configuration​

Redirect URI changes in authentik 2026.5

In authentik versions earlier than 2026.5, all Redirect URIs are automatically treated as Authorization type. If you are using one of these older authentik versions, add only the Authorization URL to your Redirect URIs and do not configure a Post Logout URI.

To support the integration of Fluxer with authentik, you need to create an application/provider pair in authentik.

Email verification​

Fluxer rejects SSO logins with an unverified email address when the instance uses email sign-in, or when Allowed Email Domains is set in Fluxer's SSO settings. The default authentik email scope mapping returns email_verified: false. In either case, create a custom email scope mapping as described in Verify email addresses. Fluxer shows the instance's sign-in method in the admin panel under Configuration > Instance Config > Sign-in Method.

Create an application and provider​

  1. Log in to authentik as an administrator and open the authentik Admin interface.

  2. Navigate to Applications > Applications and click New Application to open the application wizard.

    • Application: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Note the Slug value because it will be required later.
    • Choose a Provider type: select OAuth2/OpenID Connect as the provider type.
    • Configure the Provider: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and the following required configurations.
      • Note the Client ID and Client Secret values because they will be required later.
      • Add a Redirect URI of type Strict Authorization with a value of https://fluxer.company/auth/sso/callback.
      • Select any available signing key.
      • If you created a custom email scope mapping, open Advanced protocol settings, add it to Selected Scopes, and remove authentik default OAuth Mapping: OpenID 'email'.
    • Configure Bindings (optional): you can create a binding (policy, group, or user) to manage the listing and access to applications on a user's Application Dashboard page.

  3. Click Submit to save the new application and provider.

Fluxer configuration​

Configure SSO​

Private addresses

Fluxer only accepts identity provider URLs that use HTTPS and resolve to a public address. If authentik.company resolves to a private address, allow private addresses before you configure SSO. On an instance that rexctl manages, run the following command:

rexctl config set FLUXER_SSO_ALLOW_PRIVATE_ADDRESSES true

On other installations, set FLUXER_SSO_ALLOW_PRIVATE_ADDRESSES=true in Fluxer's environment and restart Fluxer.

  1. Log in to the Fluxer admin panel at https://fluxer.company/admin as an administrator.
  2. Navigate to Configuration > Instance Config and locate the Single Sign-On (SSO) card.
  3. Configure the following settings:
    • Enable SSO: select this option.
    • Automatically provision users on first SSO login: select this option to create a Fluxer account for an authentik user on their first login.
    • Display Name: authentik
    • Issuer: https://authentik.company/application/o/<application_slug>/
    • Client ID: Client ID from authentik
    • Client Secret: Client Secret from authentik
  4. Confirm that the Redirect URI field shows https://fluxer.company/auth/sso/callback.
  5. Click Save SSO Settings.

On an instance that uses email sign-in, Fluxer links an SSO login to the existing Fluxer account with the same email address. On an instance that uses username sign-in, Fluxer cannot link existing accounts, so a user's first SSO login creates a new account when automatic provisioning is enabled.

Require SSO (optional)​

To disable password and passkey login and local registration, select Require SSO in the Single Sign-On (SSO) card and click Save SSO Settings. Before you enable this setting, confirm that at least one Fluxer administrator can log in through authentik. On an instance that uses username sign-in, an administrator's first SSO login creates a new account without administrator rights. Grant that account administrator rights, for example with rexctl admins add <username>.

Configuration verification​

To confirm that authentik is properly configured with Fluxer, log out of Fluxer, open Fluxer, and click Continue with authentik. You should be redirected to authentik and then returned to Fluxer after a successful login.

Resources​