Skip to main content

Integrate with FreshRSS

Support level: Community

What is FreshRSS?​

FreshRSS is a self-hosted RSS feed aggregator.

-- https://freshrss.org/

Preparation​

The following placeholders are used in this guide:

  • freshrss.company is the FQDN of the FreshRSS 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 FreshRSS with authentik, you need to create an application/provider pair in authentik.

Create an application and provider in authentik​

  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 application Slug 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 two Redirect URIs of type Strict Authorization as https://freshrss.company/i/oidc/ and https://freshrss.company:443/i/oidc/. If FreshRSS is exposed on a port other than 443, update the second redirect URI accordingly.
      • Select any available signing key.
    • 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.

FreshRSS configuration​

FreshRSS image support

FreshRSS OIDC support is available in the Debian-based FreshRSS Docker image on x86_64, or when FreshRSS runs behind an Apache server with mod_auth_openidc. The Alpine image does not include OIDC support.

Administrator access

Before restarting FreshRSS with OIDC enabled, make sure at least one FreshRSS admin username matches the preferred_username value of an authentik user.

To enable OIDC login with FreshRSS, update your .env file to include the following variables:

.env
OIDC_ENABLED=1
OIDC_PROVIDER_METADATA_URL=https://authentik.company/application/o/<application_slug>/.well-known/openid-configuration
OIDC_CLIENT_ID=<Client ID from authentik>
OIDC_CLIENT_SECRET=<Client Secret from authentik>
OIDC_CLIENT_CRYPTO_KEY=<Random string>
OIDC_X_FORWARDED_HEADERS=X-Forwarded-Port X-Forwarded-Proto X-Forwarded-Host
OIDC_SCOPES=openid email profile

Restart FreshRSS after changing these settings. Log in as a user that exists in both FreshRSS and authentik, then go to Settings > Authentication and set Authentication method to HTTP (for advanced users with HTTPS).

If you are configuring a new FreshRSS installation, enable OIDC before completing the setup wizard. When the setup wizard asks for the default user, use the exact username from authentik. In the authentication setup step, select HTTP Authentication Method.

Configuration verification​

To confirm that authentik is properly configured with FreshRSS, log out of FreshRSS and open the integration. FreshRSS should redirect you to authentik and then return you to FreshRSS as the matching user.

Resources​