Skip to content

Commit 0ffde36

Browse files
authored
chore(docs): update of OEL images (ory#2647)
chore(docs): update OEL image tag
1 parent cc78f33 commit 0ffde36

10 files changed

Lines changed: 65 additions & 0 deletions

File tree

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
No changelog entries found for keto/oel in versions v26.2.22
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
## v26.2.22
2+
3+
### Support multiple passkey display-name traits in identity schemas
4+
5+
Identity schemas can now flag more than one trait with `passkey.display_name: true` or `webauthn.identifier: true`. Creating a
6+
registration flow no longer fails with HTTP 500 and `"no identifier found"` when both `email` and `phone` (or any other
7+
combination) are flagged as passkey display-name sources.
8+
9+
The browser picks the first form field that the user actually filled in, so the same schema can serve email-only and phone-only
10+
signup paths without breaking either one. Schemas that flag a single trait, or none at all, continue to work as before.
11+
12+
The fix is backward compatible. Custom registration UIs that parse `passkey_create_data` and read the existing
13+
`displayNameFieldName` field continue to work; the new `displayNameFieldNames` array is published alongside it for clients that
14+
want the full candidate list.
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
No changelog entries found for oathkeeper/oel in versions v26.2.22
Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
## v26.2.22
2+
3+
### Much faster OAuth2 logout
4+
5+
This change improves performance of OAuth2/OpenID Connect logout by moving to a database-free implementation. Logout challenges
6+
and verifiers are now self-contained encrypted tokens instead of database rows, and the lookup of clients registered for front-
7+
and back-channel logout uses a single indexed query.
8+
9+
The behavior of APIs and user interactions are unchanged. The admin endpoint `GET /admin/oauth2/auth/requests/logout` no longer
10+
returns `410 Gone` for already-handled logout requests, because handled state no longer exists.
11+
12+
Upgrade notes:
13+
14+
- Run SQL migrations before rolling out this version. The new client lookup query requires the index added by this release; on
15+
CockroachDB the query fails if the index is missing.
16+
- Logout flows that are in flight while the upgrade rolls out fail with "logout request expired". Users retrying complete normally
17+
on the new version.
18+
19+
### Revoke login sessions by subject in batches
20+
21+
Revoking all login sessions for a subject through `DELETE /admin/oauth2/auth/sessions/login?subject=...` now deletes the sessions
22+
in bounded batches instead of a single statement.
23+
24+
Previously, a subject with a very large number of login sessions produced a single, very large delete that could exceed the
25+
database's transaction limits or time out, failing with a "context canceled" error and leaving the sessions in place. Deleting in
26+
batches keeps each transaction small, so the request completes reliably regardless of how many sessions a subject has.
27+
28+
The endpoint's behavior is unchanged for callers: all matching login sessions are removed. If the request is canceled partway
29+
through, the sessions deleted so far stay deleted and the call can be safely retried to finish the rest.

docs/self-hosted/oel/oel-hydra-image-tags.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
| Image Tag | Release Date |
22
| ---------------------------------------- | ------------ |
3+
| 26.2.22 | 2026-06-26 |
34
| 26.2.21 | 2026-06-23 |
45
| 26.2.20 | 2026-06-19 |
56
| 26.2.19 | 2026-06-17 |

docs/self-hosted/oel/oel-keto-image-tags.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
| Image Tag | Release Date |
22
| ---------------------------------------- | ------------ |
3+
| 26.2.22 | 2026-06-26 |
34
| 26.2.21 | 2026-06-23 |
45
| 26.2.20 | 2026-06-19 |
56
| 26.2.19 | 2026-06-17 |

docs/self-hosted/oel/oel-kratos-image-tags.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
| Image Tag | Release Date |
22
| ---------------------------------------- | ------------ |
3+
| 26.2.22 | 2026-06-26 |
34
| 26.2.21 | 2026-06-23 |
45
| 26.2.20 | 2026-06-19 |
56
| 26.2.19 | 2026-06-17 |

docs/self-hosted/oel/oel-oathkeeper-image-tags.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
| Image Tag | Release Date |
22
| ---------------------------------------- | ------------ |
3+
| 26.2.22 | 2026-06-26 |
34
| 26.2.21 | 2026-06-23 |
45
| 26.2.20 | 2026-06-19 |
56
| 26.2.19 | 2026-06-17 |

docs/self-hosted/oel/oel-polis-image-tags.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
| Image Tag | Release Date |
22
| ---------------------------------------- | ------------ |
3+
| 26.2.22 | 2026-06-26 |
34
| 26.2.21 | 2026-06-23 |
45
| 26.2.20 | 2026-06-19 |
56
| 26.2.19 | 2026-06-17 |
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
## v26.2.22
2+
3+
### Fix cross-tenant identity provider selection via idp_hint in Polis
4+
5+
The `idp_hint` parameter on the SAML Identity Federation and SSO endpoints selected an upstream identity provider connection by id
6+
without checking that the connection belonged to the requesting tenant and product. On a multi-tenant deployment, a co-tenant
7+
could supply the id of a connection in their own tenant as `idp_hint` for another tenant's federation app, routing the login to an
8+
identity provider they control and obtaining a Polis-signed assertion audienced to the victim's downstream service provider.
9+
10+
Polis now scopes the hinted connection to the requesting flow. A hint is accepted only when the connection belongs to the
11+
requested tenant and product, to one of a multi-tenant federation app's tenants, or — for IdP-initiated SSO — to the identity
12+
provider that issued the response. Out-of-scope hints are rejected with `403`. The upstream-response callback re-checks that the
13+
selected connection is within the session's tenant scope.
14+
15+
In-scope use of `idp_hint`, including for multi-tenant federation apps, is unchanged.

0 commit comments

Comments
 (0)