Tim Möhlmann ad9422a7d0 fix(crypto): check for nil client secret (#7729) ... When creating an app without secret or other type of authentication method, like JWT, and the authentication type is switched afterwards the app would remain without generated secret. If then client authentication with secret is attempted, for example on the token endpoint, the handler would panic in the crypto.CompareHash function on the nile pointer to the CryptoValue. This fix introduces a nil pointer check in crypt.CompareHash and returns a error. The issue was reported over discord: https://discord.com/channels/927474939156643850/1222971118730875020 Possible fix was suggested here: https://github.com/zitadel/zitadel/pull/6999#discussion_r1553503088 This bug only applies to zitadel versions <=2.49.1.		2024-04-09 08:44:52 +02:00
..
bg.yaml	fix(crypto): check for nil client secret (#7729)	2024-04-09 08:44:52 +02:00
cs.yaml	fix(crypto): check for nil client secret (#7729)	2024-04-09 08:44:52 +02:00
de.yaml	fix(crypto): check for nil client secret (#7729)	2024-04-09 08:44:52 +02:00
en.yaml	fix(crypto): check for nil client secret (#7729)	2024-04-09 08:44:52 +02:00
es.yaml	fix(crypto): check for nil client secret (#7729)	2024-04-09 08:44:52 +02:00
fr.yaml	fix(crypto): check for nil client secret (#7729)	2024-04-09 08:44:52 +02:00
it.yaml	fix(crypto): check for nil client secret (#7729)	2024-04-09 08:44:52 +02:00
ja.yaml	fix(crypto): check for nil client secret (#7729)	2024-04-09 08:44:52 +02:00
mk.yaml	fix(crypto): check for nil client secret (#7729)	2024-04-09 08:44:52 +02:00
nl.yaml	fix(crypto): check for nil client secret (#7729)	2024-04-09 08:44:52 +02:00
pl.yaml	fix(crypto): check for nil client secret (#7729)	2024-04-09 08:44:52 +02:00
pt.yaml	fix(crypto): check for nil client secret (#7729)	2024-04-09 08:44:52 +02:00
ru.yaml	fix(crypto): check for nil client secret (#7729)	2024-04-09 08:44:52 +02:00
zh.yaml	fix(crypto): check for nil client secret (#7729)	2024-04-09 08:44:52 +02:00