Overview - Zitadel/zitadel

zitadel/zitadel

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
main
3afa6a2e docs: correct "complement" flow names (#11320) # Which Problems Are Solved As part of the naming inconsistencies (#5888) we want to ensure action v1 flow name are always correct and mapping to enum values line up: #11309 # How the Problems Are Solved Rename last "Customize SAML Response" occurrences to "Complement SAML Response" where it's referring to the flow type. There are some titles left with "customize SAML / OIDC response", which refer to the intent of customizing the outcome and not directly to the flow type. # Additional Changes None # Additional Context - closes 11309
16 hours ago by yonas
Succeeded
main
4b5d6e39 chore: update js-yaml (#11300) # Which Problems Are Solved Fixes [Dependency Security Alert](https://github.com/zitadel/zitadel/security/dependabot/379) # How the Problems Are Solved This PR adds a pnpm override to force `js-yaml@^4` to resolve to `>=4.1.1`, which contains the fix for the prototype pollution vulnerability. The override only affects the 4.x line, leaving 3.x versions unchanged. # Additional Context - Closes https://github.com/zitadel/zitadel/security/dependabot/379
2 days ago by yonas
Succeeded
main
62818d1b docs(guides): Removed Preview tag from title and updated for better readability (#11278) This PR solves #10310
3 days ago by yonas
Succeeded
main
5f34d1af chore: forward port organization v2 API changes (#11207) # Which Problems Are Solved Recent changes to the v2beta and v2 API of the organization service were directly merged to the `next` branch and release on v4.x, since the ongoing move to the relation table, blocked it from being merged into main. # How the Problems Are Solved This PR ports the following changes into main: - fix(api): correct permission check in organization v2beta service: https://github.com/zitadel/zitadel/commit/8dcfff97ed52a8b9fc77ecb1f972744f42cff3ed - fix(actions v1): return org metadata again (https://github.com/zitadel/zitadel/pull/11040) - feat(api): move organization api (https://github.com/zitadel/zitadel/pull/11045) # Additional Changes None # Additional Context relates to #10772 --------- Co-authored-by: Gayathri Vijayan <66356931+grvijayan@users.noreply.github.com>
4 days ago by yonas
Succeeded
main
ee6d66d4 docs(Guides): Add PingFederate SAML IdP guide (#11244) This solves issue #10545
9 days ago by yonas
Succeeded
main
740669a4 docs: remove out-dated / incorrect beta labels (#11211) # Which Problems Are Solved Some features moved from Beta to GA in V4, are still labeled as beta in the docs and APIs refer to the now deprecated beta endpoints. # How the Problems Are Solved - remove the beta labels from webkeys, login v2, actions v2 - change example calls and API reference to v2 (instead of v2beta) # Additional Changes fixed typo in the web keys title (Oauth2 -> OAuth2) # Additional Context - Organization service v2(beta) is solved in https://github.com/zitadel/zitadel/pull/11207 - relates to #10772 --------- Co-authored-by: Gayathri Vijayan <66356931+grvijayan@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
11 days ago by yonas
Succeeded
main
15e89078 docs: update private key jwt for token instrospection (#11227) The current document for private key JWT is misleading, as it currently looks like a mechanism to secure an API, and it's not, this section only shows how to use private key JWT to call the introspect endpoint
16 days ago by yonas
Succeeded
main
3106dcfc docs: update database configuration page (#11219)
18 days ago by yonas
Succeeded
main
7c01deb8 fix(authorizations): comment out timestamp assertions (#11214) # Which Problems Are Solved Comment out timestamp assertions to temporarily unblock CI pipeline # How the Problems Are Solved Comment out timestamp assertions to temporarily unblock CI pipeline # Additional Changes N/A # Additional Context
21 days ago by yonas
Succeeded
main
11cf2c25 chore(ux): Fix wording for application ID token settings (#11210) When this checkbox is enabled, the user profile information (not the roles assigned) will be returned as claims in the ID token. The current wording is not accurate.
22 days ago by yonas
Succeeded
main
1ce8bcbd fix: id token had no lifetime for client credentials (#11204) # Which Problems Are Solved - ID-token had no lifetime when a token was requested using the `client_credentials` grant # How the Problems Are Solved - Take use the lifetime provided by the server. # Additional Context - Closes #11060
23 days ago by yonas
Succeeded
main
5a7136fe docs: Disable emoji rendering (#10994) # Which Problems Are Solved We had to wrap reserved scopes like `urn:zitadel:iam:org:id:178204173316174381` in a code block, because Docusaurus was rendering :id: as emoji. # How the Problems Are Solved Update Docusaurus to 3.9.2. and disable the emoji rendering in markdown files. # Additional Changes # Additional Context Co-authored-by: Florian Forster <florian@zitadel.com>
23 days ago by yonas
Succeeded
main
2221b5ef fix(login): CVE-2025-55184 and CVE-2025-55183, update next (#11179) # Which Problems Are Solved Updates `next` to version `15.5.9` to address the following security vulnerabilities: - **CVE-2025-55184** - **CVE-2025-55183** # How the Problems Are Solved - Bump `next` from `15.5.7` to `15.5.9` in `apps/login/package.json` --------- Co-authored-by: PhenixH <PhenixH@users.noreply.github.com>
28 days ago by yonas
Succeeded
main
d2d85bd3 fix(email): accept SMTPUTF8 addresses (#11115) # Which Problems Are Solved Zitadel only accepted ASCII email addresses, while some users need to enter internationalized addresses. For example `möhlmann@example.com` # How the Problems Are Solved - Use `net/mail` to validate email addresses, instead of a custom regex. `net/mail` correctly accepts UTF-8 characters. - In the management/v1 API email address validation is removed (only string limits are applied) # Additional Changes - none # Additional Context Closes https://github.com/zitadel/zitadel/issues/9821
29 days ago by yonas
Succeeded
main
826039c6 Merge commit from fork * Force v2 permission checks on user listing * Remove duplicated tests * cleanup and fix tests --------- Co-authored-by: Livio Spring <livio.a@gmail.com>
29 days ago by yonas
Succeeded
main
dfe064f9 fix(login): fix back button on 2fa screen to allow username change (#11125) # Which Problems Are Solved As reported to support, the back button on the various 2FA pages in login V1 opened the default redirect URI, which likely started a new auth request (e.g. from Console). # How the Problems Are Solved Change the back buttons to navigate to the login screen again, where a user can change the username. Additionally, the back button has been added to the U2F verification screen. # Additional Changes None # Additional Context - from support - backport to v4
1 month ago by yonas
Succeeded
main
df75be96 Merge commit from fork * fix: Improve host header handling and deployment mode detection * ZITADEL_CLOUD env * refactor service config * service config * cleanup * cleanup * util for original and public host * instanceHost, publicHost * cleanup constructUrl * cleanup middleware * add x-zitadel-forward-host as fallback for current cloud setup * fix build * fix: lint * fix: update test mocks * fix: provide basepath to unit tests * host handling * unit tests * imports * fix: getPublicHost instead of getInstanceHost * unit tests * update nextjs, implement jwt verify for logout_token * pass logout information in jwt to login v2 * handle hosts in jwks url * point idp callbacks to the api and not the login UI * logout_hint out of logout token, typecheck * rm unused imports * fix oidc integration test --------- Co-authored-by: Livio Spring <livio.a@gmail.com>
1 month ago by yonas
Succeeded
main
f9e3871b docs: add rest paths to api design (#9910) # Which Problems Are Solved REST paths for new APIs are unclear as they are not defined in the API_DESIGN. # How the Problems Are Solved Add a part to the API_DESIGN, which can be removed at a later date when migrating to RPC connect. # Additional Changes None # Additional Context None
1 month ago by yonas
Succeeded
main
e26859d6 fix(domain): use `crypto.CryptoValue` (#11131) Update the `Check` struct to utilize `crypto.CryptoValue` for the `Code` field, enhancing security and type safety. Adjust the `CheckTypeInit` struct accordingly to maintain consistency.
1 month ago by yonas
Succeeded
main
6e747172 chore(console): explain that a project can contain multiple applications that would b… (#11103) # Which Problems Are Solved It's unclear to new users that a single web application might have more than one Zitadel "application", like one for the frontend and one for the backend. # How the Problems Are Solved Updates the text defining projects in the onboarding # Additional Changes None # Additional Context Working on general improvements to make onboarding easier. --------- Co-authored-by: David Skewis <david@zitadel.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
1 month ago by yonas