v2 Session Search Queries don't apply at all.
āUnsolvedšŖ²Bugs
Use-case:
We want to logout users from all sessions in our application by the press of a button. For that we want to find each active session via the v2 REST API route /sessions/search , then iterate the returned list and call DELETE sessions/<sessions-id>
Environment: Self hosted
Version: v4.16.1
Stack:
We are self hosting Zitadel v4.16.1, which resides in a docker container and is reachable via a Traefik reverse proxy.
We use OIDC and use https://github.com/sevensolutions/traefik-oidc-auth as a Traefik OIDC Plugin.
To configure Zitadel, we use .env files which contain various variables from the defaults.yml and steps.yml file (we prefer using .env directly instead of .yml files). Other aspects, such as organisations, projects, applications, etc are created at container start via a bash script and REST API.
Our backend is written in Python.
What you expected to happen:
We call this route to fetch all existing session IDs of a user:
response = requests.post("http://zitadel-api:8080/v2/sessions/search",
json={
"queries": [
{
"userIdQuery": {
"id": f"{idp_id}"
}
}
]
},
headers={
'Authorization': f'Bearer {idp_admin_access_token}',
'Host': 'localhost:8800'
}
)
This should, according to the docs, return both a json body containing fields named "details" and "sessions". The later of which would contain the session IDs we can then iterate and delete & add to an internal blocklist (https://zitadel.com/docs/reference/api/session/zitadel.session.v2.SessionService.ListSessions?utm_source=openai)
We want to logout users from all sessions in our application by the press of a button. For that we want to find each active session via the v2 REST API route /sessions/search , then iterate the returned list and call DELETE sessions/<sessions-id>
Environment: Self hosted
Version: v4.16.1
Stack:
We are self hosting Zitadel v4.16.1, which resides in a docker container and is reachable via a Traefik reverse proxy.
We use OIDC and use https://github.com/sevensolutions/traefik-oidc-auth as a Traefik OIDC Plugin.
To configure Zitadel, we use .env files which contain various variables from the defaults.yml and steps.yml file (we prefer using .env directly instead of .yml files). Other aspects, such as organisations, projects, applications, etc are created at container start via a bash script and REST API.
Our backend is written in Python.
What you expected to happen:
We call this route to fetch all existing session IDs of a user:
response = requests.post("http://zitadel-api:8080/v2/sessions/search",
json={
"queries": [
{
"userIdQuery": {
"id": f"{idp_id}"
}
}
]
},
headers={
'Authorization': f'Bearer {idp_admin_access_token}',
'Host': 'localhost:8800'
}
)
This should, according to the docs, return both a json body containing fields named "details" and "sessions". The later of which would contain the session IDs we can then iterate and delete & add to an internal blocklist (https://zitadel.com/docs/reference/api/session/zitadel.session.v2.SessionService.ListSessions?utm_source=openai)
GitHub
A traefik Plugin for securing the upstream service with OpenID Connect acting as a relying party. - sevensolutions/traefik-oidc-auth
A traefik Plugin for securing the upstream service with OpenID Connect acting as a relying party. - sevensolutions/traefik-oidc-authList sessions: Searches for sessions matching the given query. You can search by session ID, user ID, creation date, creator, user agent or expiration date. Required permissions:
