-
Notifications
You must be signed in to change notification settings - Fork 660
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: zitadel/zitadel
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v2.71.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: zitadel/zitadel
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v2.71.2
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 4 commits
- 18 files changed
- 3 contributors
Commits on Mar 12, 2025
-
fix(login): passkey setup when pressing "Enter" key on login form (#9485
) # Which Problems Are Solved When registering passkeys or u2f methods as second factor, some users pressed the "Enter" key, rather than clicking the submit button. This method has bypassed the execution of the device registration and encoding scripts, resulting in the form being submitted without the necessary encoded values. # How the Problems Are Solved This PR ensures that device registration is always executed and the required information are submitted in the form regardless of pressing "Enter" or clicking the button. # Additional Changes None # Additional Context - closes #6592 - closes #2910 (cherry picked from commit 27b319b)
Configuration menu - View commit details
-
Copy full SHA for 6256908 - Browse repository at this point
Copy the full SHA 6256908View commit details -
fix(token exchange): properly return an error if membership is missing (
#9468) # Which Problems Are Solved When requesting a JWT (`urn:ietf:params:oauth:token-type:jwt`) to be returned in a Token Exchange request, ZITADEL would panic if the `actor` was not granted the necessary permission. # How the Problems Are Solved Properly check the error and return it. # Additional Changes None # Additional Context - closes #9436 (cherry picked from commit e6ce1af)
Configuration menu - View commit details
-
Copy full SHA for 5ad33e7 - Browse repository at this point
Copy the full SHA 5ad33e7View commit details -
fix(OIDC): back channel logout work for custom UI (#9487)
# Which Problems Are Solved When using a custom / new login UI and an OIDC application with registered BackChannelLogoutUI, no logout requests were sent to the URI when the user signed out. Additionally, as described in #9427, an error was logged: `level=error msg="event of type *session.TerminateEvent doesn't implement OriginEvent" caller="/home/runner/work/zitadel/zitadel/internal/notification/handlers/origin.go:24"` # How the Problems Are Solved - Properly pass `TriggerOrigin` information to session.TerminateEvent creation and implement `OriginEvent` interface. - Implemented `RegisterLogout` in `CreateOIDCSessionFromAuthRequest` and `CreateOIDCSessionFromDeviceAuth`, both used when interacting with the OIDC v2 API. - Both functions now receive the `BackChannelLogoutURI` of the client from the OIDC layer. # Additional Changes None # Additional Context - closes #9427 (cherry picked from commit ed697bb)
Configuration menu - View commit details
-
Copy full SHA for a47f4a3 - Browse repository at this point
Copy the full SHA a47f4a3View commit details -
fix(eventstore): optimise query hints for event filters (#9497)
(cherry picked from commit b578137)
Configuration menu - View commit details
-
Copy full SHA for e770569 - Browse repository at this point
Copy the full SHA e770569View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v2.71.1...v2.71.2