goauthentik / goauthentik/authentik

Allow specifying outpost AUTHENTIK_TOKEN using blueprints

Open
#9,711 6 comments 2 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
25.6k
Forks
2k
Avg merge
1d 1h
Merged PRs (30d)
644

Description

**Is your feature request related to a problem? Please describe.**
I'm trying to deploy an LDAP outpost using blueprints. One of the steps is to copy the auto generated token from the outpost in Authentic into the deployment of the outpost container. This prevents me from automating deployment of clusters using LDAP.

**Describe the solution you'd like**
I would like to be able to specify the AUTHENTIK_TOKEN to use as part of the blueprint.

**Describe alternatives you've considered**
An admin user can get the token via the web apis. In my case, I could probably use this to poll it via a kubernetes job and write it to a secret that is used for the outpost's envvars. It feels pretty messy.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.