zitadel/internal/integration
Livio Spring 5b40af79f0
fix: correctly check user state (#8631)
# Which Problems Are Solved

ZITADEL's user account deactivation mechanism did not work correctly
with service accounts. Deactivated service accounts retained the ability
to request tokens, which could lead to unauthorized access to
applications and resources.

# How the Problems Are Solved

Additionally to checking the user state on the session API and login UI,
the state is checked on all oidc session methods resulting in a new
token or when returning the user information (userinfo, introspection,
id_token / access_token and saml attributes)
2024-09-17 13:21:49 +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 user state (#8631) 2024-09-17 13:21:49 +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