Skip to content

Automated install not picked up as expected #3080

@simonkaiser9

Description

@simonkaiser9

When configuring my deployment of Authentik the AUTHENTIK_BOOTSTRAP_PASSWORD configuration is not picked up as expected.
This relates to core: add bootstrap variables with authentik prefix for helm charts #3031

Steps to reproduce the behavior:

  1. Clean helm install with chart 2022.6.1
  2. Try to log into authentik with pre-configured password for akadmin
  3. Password is invalid
  4. (optional) Go to /if/flow/initial-setup: Setup is available although bootstrapped instance should be running

I'd expect the instance to be running with akadmin password and token to be set correctly and initial setup to be unavailable.

Helm values.yaml:

authentik:
   env:
      AUTHENTIK_BOOTSTRAP_PASSWORD: 'test'
      AUTHENTIK_BOOTSTRAP_TOKEN: 'test'

Environment in Kubernetes server pod:

➜  ~ k exec --tty --stdin -n authentik authentik-server-7b4b4db6db-9jlbd -- /bin/bash
authentik@authentik-server-7b4b4db6db-9jlbd:/$ env | grep BOOT
AUTHENTIK_ENV__AUTHENTIK_BOOTSTRAP_TOKEN=test
AUTHENTIK_ENV__AUTHENTIK_BOOTSTRAP_PASSWORD=test

Configuration dump:

➜  ~ kubectl exec -it deployment/authentik-worker -c authentik -- ak dump_config
*** redacted ***
    "env": {
        "authentik_bootstrap_token": "test",
        "authentik_bootstrap_password": "test"
    },
*** redacted ***
}

Version and Deployment (please complete the following information):

  • authentik version: 2022.6.2
  • Deployment: helm chart 2022.6.1

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions