3 people a8861336f4 fix(api): accept SetSecuritySettings on /v2/settings/security (#12518) ...

# Which Problems Are Solved

`GetSecuritySettings` is served at `GET /v2/settings/security`, but
`SetSecuritySettings` was only bound to `PUT /v2/policies/security`.
That split made the natural copy-paste path (`PUT
/v2/settings/security`)
return `405`, including the enable curl in the Dynamic Client
Registration
guide.

# How the Problems Are Solved

Make `PUT /v2/settings/security` the primary HTTP binding for
`SetSecuritySettings`, and keep `PUT /v2/policies/security` as an
`additional_bindings` entry so existing callers keep working.

# Additional Changes

None.

# Additional Context

- Noticed during review of the Dynamic Client Registration PR (#12313):
the
guide's enable curl used `PUT /v2/settings/security` and hit `405`
against a
  live instance.
- Only `settings/v2` is changed; `v2beta` is left as-is (deprecated).
- Generated gateway/OpenAPI artifacts are gitignored and rebuilt from
the
  proto on generate.

Co-authored-by: Cursor <[email protected]>

2026-07-31 11:34:00 +02:00

..

zitadel

fix(api): accept SetSecuritySettings on /v2/settings/security (#12518)

2026-07-31 11:34:00 +02:00

AGENTS.md

chore(agents): add agents files (#11497)

2026-02-16 20:45:53 -08:00

buf.lock

chore(console): buf stub build (#5215)

2023-02-17 14:09:11 +00:00

buf.yaml

fix: query organization directly from event store (#10463)

2025-08-12 09:37:08 +00:00