Fits how you already work

Ready-made plugins

• LDAP
• Active Directory
• OpenID Connect
• SAML, ADFS and Shibboleth
• Microsoft Azure
• OAuth2
• Authentik
• Google
• Dropbox and Box

Any OpenID Connect provider

Keycloak, Authentik, Authelia, Microsoft Entra ID, Google and anything else that follows the standard. FileRun reads the provider's configuration from its discovery address, so there is very little to type in.
Signing out works in both directions: the provider ends the FileRun session, and FileRun ends the session at the provider.

On a Windows domain

With Integrated Authentication, users who are already signed in to Windows are signed in to FileRun automatically. They type nothing.

Or no directory at all

FileRun keeps its own accounts as well, and they can be opened with a passkey — a fingerprint, a face, a device PIN or a USB security key.

Building on it

• A full REST API, described in OpenAPI, so you can generate a client for whichever language you work in.
• OAuth2, with tokens you can limit to only what the program needs. A "comments" scope, for example, lets an application write comments and reach nothing else.
• Access tokens are cryptographically signed, so they cannot be forged or altered.
• A PHP client library, if that is what you write in.

Connecting it to your own systems

• Create, change and remove user accounts from your own software, so your joiners and leavers process stays where it already is.
• Groups, roles, comments, tags, file locking and the trash are reachable as well, not only files and accounts.
• The API uses the same permission checks as the web interface. What a user cannot do in the browser, they cannot do through the API.
• It can be turned off on its own, separately from web, WebDAV, desktop and mobile.