Livio Spring f1a5c0fc76 fix: correctly check app state on authentication (#8630) ... # Which Problems Are Solved In Zitadel, even after an organization is deactivated, associated projects, respectively their applications remain active. Users across other organizations can still log in and access through these applications, leading to unauthorized access. Additionally, if a project was deactivated access to applications was also still possible. # How the Problems Are Solved - Correctly check the status of the organization and related project. (Corresponding functions have been renamed to `Active...`) (cherry picked from commit d01bd1c51a)		2024-09-17 15:35:32 +02:00
..
auth_request_test.go	chore(tests): use a coverage server binary (#8407)	2024-09-06 14:47:57 +02:00
client_test.go	fix: correctly check app state on authentication (#8630)	2024-09-17 15:35:32 +02:00
keys_test.go	chore(tests): use a coverage server binary (#8407)	2024-09-06 14:47:57 +02:00
oidc_test.go	chore(tests): use a coverage server binary (#8407)	2024-09-06 14:47:57 +02:00
server_test.go	chore(tests): use a coverage server binary (#8407)	2024-09-06 14:47:57 +02:00
token_client_credentials_test.go	chore(tests): use a coverage server binary (#8407)	2024-09-06 14:47:57 +02:00
token_exchange_test.go	chore(tests): use a coverage server binary (#8407)	2024-09-06 14:47:57 +02:00
token_jwt_profile_test.go	chore(tests): use a coverage server binary (#8407)	2024-09-06 14:47:57 +02:00
userinfo_test.go	chore(tests): use a coverage server binary (#8407)	2024-09-06 14:47:57 +02:00