7 docs tagged with "expression"

Use an expression policy when only specific email domains should be allowed to enroll or authenticate.

By default, authentik does not require email addresses to be unique. If you want to enforce uniqueness, use an expression policy during enrollment or profile-edit flows.

By default, authentik compares usernames case-sensitively when checking whether a username is already taken, so user1 and User1 can exist as two separate users. The Identification stage matches identifiers case-insensitively by default, so when both users exist, entering either username finds only one of them.

Expression policies let you write custom Python for cases where the built-in policy types are not enough.

This page documents the expression policy execution environment in authentik.

Flow context can be read and updated from an Expression policy through context"flow_plan"].context. For more information about the active plan, see [Flow Planner.

You can use an expression policy to route users to different sources based on the email address they enter.