Configure

Authentication integration🔗

FileRun ships authentication plugins for:

• OpenID Connect — any provider that supports the standard: Keycloak, Authelia, Microsoft Entra ID, Google and others.
• Authentik — two plugins, one using OpenID Connect and a deprecated OAuth2 one.
• OAuth2 — for a provider that speaks OAuth2 but not OpenID Connect.
• LDAP and Active Directory — the same plugin, configured differently.
• SimpleSAMLphp — for SAML, Shibboleth, Active Directory Federation Services (ADFS) and similar.
• Microsoft Entra ID — formerly Azure Active Directory.
• Google
• Dropbox
• Box.com

Only one plugin can be enabled at a time. Select it from the Enabled plugin list.

Note

The WordPress plugin was removed in FileRun 2026.3.0. Installations that were using it fall back to the built-in authentication. WordPress can still be connected through the OpenID Connect or OAuth2 plugin, using a WordPress provider plugin.

Before you enable authentication integration, please use the Save and test settings button to make sure the settings are correct.

Important

Undo the settings changes if the test is not successful

In case you configured the settings incorrectly or the third-party system stops working, in most cases you will still be able to login with the FileRun superuser login (with the password last stored in FileRun's own database).

Single-sign-on (SSO)🔗

The authentication plugins for the CMS systems support single-sign-on, so that users authenticated in your site, are not required to type in their usernames and passwords again, for accessing FileRun. For this to work, after the users logged into your site, you need to redirect them to http://your-site.com/filerun/sso/ (note the /sso/ ending). If you direct them to the FileRun root URL and the authentication settings allow local login (login with FileRun credentials), the users will be prompted by the login form and not redirected automatically.

Disabling the authentication integration🔗

In case you can no longer access the FileRun control panel, please follow these steps:

1. Run the following SQL query on the FileRun database:

    1UPDATE `fr_core_settings` SET `val`='' WHERE `var`='auth_plugin'
   

   On a FileRun version older than 2026.3.0, the table is named df_settings.

2. Delete the file system/data/temp/cache/settings.tmp.php

You should now be able to log in FileRun with the previously set FileRun superuser credentials.