Livio Spring 0af37d45e9 fix: handle user remove correctly in v1 sessions for login (#8432) ... # Which Problems Are Solved In case a user was deleted and recreated with the same id, they would never be able to authenticate through the login UI, since it would return an error "User not active". This was due to the check in the auth request / session handling for the login UI, where the user removed event would terminate an further event check and ignore the newly added user. # How the Problems Are Solved - The user removed event no longer returns an error, but is handled as a session termination event. (A user removed event will already delete the user and the preceding `activeUserById` function will deny the authentication.) # Additional Changes Updated tests to be able to handle multiple events in the mocks. # Additional Context closes https://github.com/zitadel/zitadel/issues/8201 Co-authored-by: Silvan <silvan.reusser@gmail.com>		2024-08-15 05:39:54 +00:00
..
eventsourcing/model	refactor(fmt): run gci on complete project (#7557)	2024-04-03 10:43:43 +00:00
view	fix: handle user remove correctly in v1 sessions for login (#8432)	2024-08-15 05:39:54 +00:00