Tim Möhlmann db8d794794

fix(oidc): ignore algorithm for legacy signer (#9148) ...

# Which Problems Are Solved

It was possible to set a diffent algorithm for the legacy signer. This
is not supported howerver and breaks the token endpoint.

# How the Problems Are Solved

Remove the OIDC.SigningKeyAlgorithm config option and hard-code RS256
for the legacy signer.

# Additional Changes

- none

# Additional Context

Only RS256 is supported by the legacy signer. It was mentioned in the
comment of the config not to use it and use the webkeys resource
instead.

- closes #9121

2025-01-08 08:40:33 +00:00

..

admin

chore: test server for direct resource access

2023-04-24 20:40:31 +03:00

build

fix: allow version to be overwritten by build again (#4656)

2022-11-07 09:50:44 +00:00

encryption

feat: action v2 signing (#8779)

2024-11-28 10:06:52 +00:00

hooks

feat: support whole config as env (#6336)

2024-02-16 16:04:42 +00:00

initialise

refactor(eventstore): move push logic to sql (#8816)

2024-12-04 13:51:40 +00:00

key

feat: api v2beta to api v2 (#8283)

2024-07-26 22:39:55 +02:00

mirror

feat: action v2 signing (#8779)

2024-11-28 10:06:52 +00:00

ready

feat(v3alpha): web key resource (#8262)

2024-08-14 14:18:14 +00:00

setup

perf(fields): create index for instance domain query (#9146)

2025-01-07 16:06:33 +00:00

start

fix(idp): prevent server errors for idps using form post for callbacks (#9097)

2025-01-06 10:47:46 +01:00

tls

fix: enable env vars in setup steps (and deprecate admin subcommand) (#3871)

2022-06-27 10:32:34 +00:00

defaults.yaml

fix(oidc): ignore algorithm for legacy signer (#9148)

2025-01-08 08:40:33 +00:00

zitadel.go

fix(mirror): read config correctly (#8330)

2024-07-18 14:00:58 +00:00