Skip to main content

Integrate with Glitchtip

Support level: Community

What is Glitchtip?​

Bugs are inevitable in web development. The important thing is to catch them when they appear. With GlitchTip, you can rest easy knowing that if your web app throws an error or goes down, you will be notified immediately. GlitchTip combines error tracking and uptime monitoring in one open-source package to keep you and your team fully up-to-date on the status of your projects.

-- https://glitchtip.com/documentation

Preparation​

The following placeholders are used in this guide:

  • glitchtip.company is the FQDN of the Glitchtip 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 Glitchtip 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.
  • 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, Client Secret, and slug values because they will be required later.
    • Add a Redirect URI of type Strict Authorization as https://glitchtip.company/accounts/oidc/authentik/login/callback/.
    • 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.
  1. Click Submit to save the new application and provider.

Glitchtip configuration​

Configuration of OpenID Connect providers in Glitchtip is done using Django Admin.

  1. Create a superuser using the manage.py script:
sudo docker exec -it glitchtip-web-1 ./manage.py createsuperuser

  1. Go to https://glitchtip.company/admin/socialaccount/socialapp/ and log in with the newly-created superuser.

  2. Click Add Social Application and enter the following details:

  • Provider: OpenID Connect
  • Provider ID: authentik (should match the Redirect URI configured above)
  • Provider Name: Whatever you want to appear on GlitchTip's log in button
  • Client ID: <Client ID from authentik>
  • Secret key: <Client Secret from authentik>
  • Key: leave blank
  • Settings: {"server_url": "https://authentik.company/application/o/<application_slug>/"} The URL should match the OpenID Configuration Issuer URL for the authentik provider.

This will add a Log in with Authentik button to the GlitchTip log in page. To add an authentik account to an existing GlitchTip account, log in using the username/password, click Profile, then click Add Account in the Social Auth Accounts section.