zitadel/internal/integration
Livio Spring d01bd1c51a
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...`)
2024-09-17 11:34:14 +00:00
..
config fix(projection): increase transaction duration (#8632) 2024-09-17 10:08:13 +00:00
sink chore(tests): use a coverage server binary (#8407) 2024-09-06 14:47:57 +02:00
assert_test.go feat: impersonation roles (#7442) 2024-02-28 10:21:11 +00:00
assert.go chore(tests): use a coverage server binary (#8407) 2024-09-06 14:47:57 +02:00
client.go feat: user v3 api update (#8582) 2024-09-17 08:27:48 +00:00
config.go chore(tests): use a coverage server binary (#8407) 2024-09-06 14:47:57 +02:00
instance.go chore(tests): use a coverage server binary (#8407) 2024-09-06 14:47:57 +02:00
oidc.go fix: correctly check app state on authentication (#8630) 2024-09-17 11:34:14 +00:00
rand.go feat: restrict languages (#6931) 2023-12-05 11:12:01 +00:00
system.go chore(tests): use a coverage server binary (#8407) 2024-09-06 14:47:57 +02:00
user.go chore(tests): use a coverage server binary (#8407) 2024-09-06 14:47:57 +02:00
usertype_enumer.go chore(tests): use a coverage server binary (#8407) 2024-09-06 14:47:57 +02:00