Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/self-hosted/oel/keto/changelog/v26.2.2.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
No changelog entries found for keto/oel in versions v26.2.2
30 changes: 30 additions & 0 deletions docs/self-hosted/oel/kratos/changelog/v26.2.2.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
## v26.2.2

### Phone number verification with SMS code

You can now verify phone numbers through the standalone verification flow, not just as a side effect of registration. When an SMS
courier channel is configured, the verification page accepts both email addresses and phone numbers.

- The verification form input label changes to "Email or phone number" when an SMS channel is configured. Without an SMS channel,
the label remains "Email".
- Submitting a phone number sends a verification code via SMS.
- The UI shows SMS-specific confirmation and success messages instead of email-specific ones.
- Unknown phone numbers are handled silently (no SMS is sent) to prevent enumeration and avoid SMS costs.

### Update identity traits and metadata from OIDC claims on login

You can now configure OIDC providers to automatically update identity traits and metadata from the upstream provider's claims on
every login — not just during registration.

Set `update_identity_on_login` to `automatic` on any OIDC provider to enable this. The same Jsonnet claims mapper that runs during
registration will re-run on each login. If the mapper output differs from the stored identity, traits and metadata are updated
before post-login hooks run.

The mapper receives the current identity as `std.extVar('identity')` with `traits`, `metadata_public`, and `metadata_admin`, so
you can write conditional logic that preserves existing values or merges selectively.

When the mapper omits `metadata_public` or `metadata_admin` from its output, existing values are preserved. When it explicitly
outputs `{}`, the fields are cleared.

This setting is available per provider in the Ory Console under advanced settings, and via the API as `update_identity_on_login`
on the provider configuration.
1 change: 1 addition & 0 deletions docs/self-hosted/oel/oathkeeper/changelog/v26.2.2.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
No changelog entries found for oathkeeper/oel in versions v26.2.2
1 change: 1 addition & 0 deletions docs/self-hosted/oel/oauth2/changelog/v26.2.2.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
No changelog entries found for hydra/oel in versions v26.2.2
1 change: 1 addition & 0 deletions docs/self-hosted/oel/polis/changelog/v26.2.2.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
No changelog entries found for polis/oel in versions v26.2.2
Loading