Tim Möhlmann 90b908c361 fix(oidc): don't push introspection client events (#8481) ... # Which Problems Are Solved Do not push secret succeeded and failed events for API and OIDC clients on the introspection endpoint. On instances where introspection was fequently called, the pushed events created issues on duplicate primary keys, due to collisions on the `sequence` column in the eventstore. As the event pusher retries on this collision and we pushed above mentioned events async, it would create a backpressure of concurrent pushers and effectively cripple an instance. We considered that pushing these events have little value with regards to the audit trail, as we do not push similar events when client assertion is used. Also, before #7657 the events were defined, but not pushed. # How the Problems Are Solved - Removed API secret check succeeded and faild event definitions - Removed OIDC secret check succeeded and faild event definitions - Push only Hash Updated event when needed # Additional Changes - None # Additional Context - Fixes https://github.com/zitadel/zitadel/issues/8479 - Closes https://github.com/zitadel/zitadel/issues/8430 - Intoduced in https://github.com/zitadel/zitadel/pull/7657		2024-08-28 18:19:50 +00:00
..
aggregate.go
api_config.go	fix(oidc): don't push introspection client events (#8481)	2024-08-28 18:19:50 +00:00
application.go
eventstore.go	fix(oidc): don't push introspection client events (#8481)	2024-08-28 18:19:50 +00:00
grant_member.go
grant.go
key.go
member.go
oidc_config.go	fix(oidc): don't push introspection client events (#8481)	2024-08-28 18:19:50 +00:00
project.go
role.go
saml_config.go