​Troubleshooting ​Basic ​Authentication

Troubleshoot issues with Basic Authentication.

Troubleshooting Scenarios

Starting with version 0.24, every open-source instance of Kestra requires Basic Authentication (username and password). You can configure credentials via the Setup Page in the UI (http://localhost:8080/ui/main/setup) or manually in the configuration file under basic-auth (recommended for production):

kestra:
  server:
    basic-auth:
      username: admin@kestra.io
      password: Admin1234

Since Basic Authentication is now required, the enabled flag is ignored and should no longer be used. Credentials must be configured to access the Kestra UI or API. For new users, simply follow the Setup Page that will show up when you start Kestra UI.

For production deployments, we recommend setting a valid email address and a strong password in the configuration file.

If you're upgrading to version 0.24, there are three possible scenarios for existing users.

Scenario 1: The enabled flag is set to true

kestra:
  server:
    basic-auth:
      enabled: true
      username: admin@kestra.io
      password: Admin1234

In this case, the following occurs:

• Now that authentication is required, it is always enabled. Therefore, the enabled flag is ignored regardless of true or false.
• The user Setup page will not appear when starting Kestra because username and password are set. You will be prompted to log in with those credentials.
• If either username or password is missing, Kestra starts with the Setup page and prompts you to create credentials. These values will be used for all future logins.
• If username or password is invalid, Kestra will show an error and prompt you to update the credentials to valid values.

Scenario 2: The enabled flag is set to false

kestra:
  server:
    basic-auth:
      enabled: false

In this case, the following occurs:

• Now that authentication is required, it is always enabled. Therefore, the enabled flag is ignored regardless of true or false.
• On first startup, the Setup page appears and prompts you to create credentials. These are stored in the Kestra database in the Settings table under the key kestra.server.basic-auth and are used for all subsequent logins.

Scenario 3: No basic-auth configuration is added

If no basic-auth configuration is defined:

• The Setup page will appear the first time starting Kestra, and you will need to create valid credentials. The authentication credentials are stored in your Kestra database in the Settings table under the key kestra.server.basic-auth. This is how you log in for all future sessions.

Scenario 4: Using Authorization headers instead of cookies

Kestra’s API accepts both Authorization: Basic ... headers and cookies for authentication. However, the UI only works with cookie-based authentication and will ignore the Authorization header.

If you are running in an environment where headers are injected automatically (e.g. via proxy or authentication middleware), you have two options:

• Use a proxy or middleware to translate the Authorization header into a BASIC_AUTH cookie before forwarding to the Kestra UI.
• Use a browser extension (e.g. ModHeader) to inject the BASIC_AUTH cookie directly.

This limitation does not affect API usage, which continues to accept both headers and cookies.