Skip to main content

Integrate with Appsmith

Support level: Community

What is Appsmith?​

Appsmith is an open-source developer tool that enables the rapid development of internal applications.

-- https://www.appsmith.com/

Preparation​

The following placeholders are used in this guide:

  • appsmith.company is the FQDN of the Appsmith 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.

Appsmith requirements

OIDC SSO is available with Appsmith Enterprise Edition. Appsmith also requires a self-hosted instance with a custom domain to configure OIDC.

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 Appsmith with authentik, you need to create an application/provider pair in authentik.

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 is 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 are required later.
      • Add a Redirect URI of type Strict Authorization with a value of https://appsmith.company/login/oauth2/code/oidc.
      • Select any available signing key.
      • Under Advanced protocol settings, add authentik default OAuth Mapping: OpenID 'offline_access' to Selected Scopes.
    • 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.

Appsmith configuration​

  1. Log in to Appsmith as an administrator.
  2. Navigate to Admin Settings > Authentication.
  3. Under OIDC, click Enable.
  4. Confirm that the Redirect URL is https://appsmith.company/login/oauth2/code/oidc.
  5. Configure the following settings:
    • Client ID: Client ID from authentik
    • Client secret: Client Secret from authentik
    • Authorization URL: https://authentik.company/application/o/authorize/
    • Token URL: https://authentik.company/application/o/token/
    • User info URL: https://authentik.company/application/o/userinfo/
    • JWK set URL: https://authentik.company/application/o/<application_slug>/jwks/
    • Scope: add offline_access.
  6. Click Save & restart and wait for the Appsmith instance to restart.

If Appsmith runs in a highly available Kubernetes deployment, restart the Appsmith deployment after saving the OIDC configuration so that all replicas use the updated settings.

Configuration verification​

To confirm that authentik is properly configured with Appsmith, open Appsmith and click Sign in with OIDC SSO. You should be redirected to authentik and returned to Appsmith after authentication.

Resources​