Skip to content

docs: team key pattern for OIDC and LDAP team sync - #218

Open
joshiste wants to merge 1 commit into
mainfrom
feat/team-key-pattern
Open

joshiste wants to merge 1 commit into
mainfrom
feat/team-key-pattern

Conversation

@joshiste

Copy link
Copy Markdown
Member

Documents the new STEADYBIT_AUTH_OAUTH2_TEAM_KEY_PATTERN and STEADYBIT_AUTH_LDAP_SYNC_TEAM_KEY_PATTERN options shipped with steadybit/platform#2044: a regular expression whose first capture group becomes the team key, matching semantics, the allow-filter effect of non-matching groups, and what changing the pattern does to already synchronized teams.

Also corrects the derivation example on the OIDC page (MY-DEVELOPERS -> MY_DEVELOPERS).

Merge on release of the platform version containing #2044.

Ticket: https://steadybitgmbh.kanbanize.com/ctrl_board/9/cards/25216

Documents STEADYBIT_AUTH_OAUTH2_TEAM_KEY_PATTERN and
STEADYBIT_AUTH_LDAP_SYNC_TEAM_KEY_PATTERN, how the first capture group
becomes the team key, the DOTALL/find matching semantics, and the
consequences of changing the pattern on an installation that already
synchronizes teams. Also corrects the derivation example, which showed
MY-DEVELOPERS where the platform produces MY_DEVELOPERS.

(ticket 25216)
@joshiste
joshiste force-pushed the feat/team-key-pattern branch from 176fabd to f6b4952 Compare September 22, 2026 14:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant