Conversation
✅ Deploy Preview for authentik-storybook canceled.
|
|
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 47.9%, saving 156.85 KB.
185 images did not require optimisation. |
👷 Deploy Preview for authentik processing.
|
✅ Deploy Preview for authentik ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7139 +/- ##
===========================================
+ Coverage 26.34% 49.28% +22.95%
===========================================
Files 568 568
Lines 28049 28049
===========================================
+ Hits 7387 13822 +6435
+ Misses 20662 14227 -6435
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
| ### Create a user | ||
|
|
||
| > If you want to automate user creation, you can do that either by [invitations](./invitations.md), [user write stage](../../flow/stages/user_write), or [using the API](/developer-docs/api/browser). | ||
|
|
There was a problem hiding this comment.
If you can automate creating new users by:
- Invitations: Invite your users to create their own accounts
- Using the API: Create user accounts through automated scripting
Looking at the contents of /stages/user_write in the API (I couldn’t find /flow/stages/user_write in the API, and the URL http://localhost:9000/if/admin/#/flow/stages/user_write in the WebUI gives me a 404), this looks much more like “how I define the user_write stage for a new user flow,” and not “how I define a new user and use the Flow to put them into the system.”
{
name: string
flow_set: [{
name: string
slug: string
title: string
designation: enum
policy_engine_mode: enum
compatibility_mode: boolean
layout: enum
denied_action: enum
}]
user_creation_mode: enum
create_users_as_inactive: boolean
user_path_template: string
}There was a problem hiding this comment.
In a future PR I will attempt to clarify the use of the user_write stage. I just want to get these basic CRUD procedurals out now.
|
authentik PR Installation instructions Instructions for docker-composeAdd the following block to your AUTHENTIK_IMAGE=ghcr.io/goauthentik/dev-server
AUTHENTIK_TAG=gh-balok-PR-1697140098-6a84386
AUTHENTIK_OUTPOSTS__CONTAINER_IMAGE_BASE=ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)sFor arm64, use these values: AUTHENTIK_IMAGE=ghcr.io/goauthentik/dev-server
AUTHENTIK_TAG=gh-balok-PR-1697140098-6a84386-arm64
AUTHENTIK_OUTPOSTS__CONTAINER_IMAGE_BASE=ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)sAfterwards, run the upgrade commands from the latest release notes. Instructions for KubernetesAdd the following block to your authentik:
outposts:
container_image_base: ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)s
image:
repository: ghcr.io/goauthentik/dev-server
tag: gh-balok-PR-1697140098-6a84386For arm64, use these values: authentik:
outposts:
container_image_base: ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)s
image:
repository: ghcr.io/goauthentik/dev-server
tag: gh-balok-PR-1697140098-6a84386-arm64Afterwards, run the upgrade commands from the latest release notes. |
Signed-off-by: Jens Langhammer <jens@goauthentik.io>
There were some HEAVY merge bugs in the translation files. * main: providers/scim: remove preview (#7166) web: bump the wdio group in /tests/wdio with 4 updates (#7160) translate: Updates for file web/xliff/en.xlf in zh_CN (#7162) translate: Updates for file web/xliff/en.xlf in zh-Hans (#7161) translate: Updates for file web/xliff/en.xlf in zh-Hans (#7158) website/docs: Balok pr for User docs (#7139)

This is an expansion of @balok's original PR in the hackathon. Full credit to Balok; I just edited and then finished writing the invitations.md topic. :-)