Overview - Zitadel/zitadel

zitadel/zitadel

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
v4.x
fc5881a9 chore: update go dependencies (#11883) Updates all dependencies to latests versions (apart from the ones where there are already issues to solve their updates). Some updates required minor changes. (cherry picked from commit f94e4065c2ff2c8c304845fa95e10f72b023af5b)
4 days ago by Livio Spring
Failed
v4.x
fc5881a9 chore: update go dependencies (#11883) Updates all dependencies to latests versions (apart from the ones where there are already issues to solve their updates). Some updates required minor changes. (cherry picked from commit f94e4065c2ff2c8c304845fa95e10f72b023af5b)
4 days ago by Livio Spring
Succeeded
main
21b28b56 fix: revert feature key for configs back to ConsoleUseV2UserApi (#11928) # Which Problems Are Solved https://github.com/zitadel/zitadel/pull/11390 renamed "Console" to "Management Console". While https://github.com/zitadel/zitadel/pull/11706 already reverted an unintended rename of the feature key to enable the management console to use the V2 API for user creation. It was now also discovered that the rename of the feature itself also broke existing (default) configurations. # How the Problems Are Solved Added a `mapstructure` tag on the instance feature to handle existing configs. # Additional Changes Removed unused `TokenExchange` from the default configuration. # Additional Context - relates to #11390 - relates to #11706 - requires backport to v4.x --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Marco A. <marco@zitadel.com>
5 days ago by Livio Spring
Succeeded
pkcs8
aa9781ac Merge b492ee0903eece983019930e73ab1773692aad52 into 9bab764796dff9f72730e629e40698f766f1e570
5 days ago by Livio Spring
Succeeded
pkcs8
be15c6b5 Merge 853278ff8d72abf9384a8838d4c2109ac6fe831c into 9bab764796dff9f72730e629e40698f766f1e570
5 days ago by Livio Spring
Succeeded
fix-org-setup-existence-check
b70de0be fix: revert feature key for configs back to ConsoleUseV2UserApi (#11928) # Which Problems Are Solved https://github.com/zitadel/zitadel/pull/11390 renamed "Console" to "Management Console". While https://github.com/zitadel/zitadel/pull/11706 already reverted an unintended rename of the feature key to enable the management console to use the V2 API for user creation. It was now also discovered that the rename of the feature itself also broke existing (default) configurations. # How the Problems Are Solved Added a `mapstructure` tag on the instance feature to handle existing configs. # Additional Changes Removed unused `TokenExchange` from the default configuration. # Additional Context - relates to #11390 - relates to #11706 - requires backport to v4.x --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Marco A. <marco@zitadel.com>
5 days ago by Livio Spring
Failed
feat/system-user-x509-via-env-file-paths
ef7577fc fix: revert feature key for configs back to ConsoleUseV2UserApi (#11928) # Which Problems Are Solved https://github.com/zitadel/zitadel/pull/11390 renamed "Console" to "Management Console". While https://github.com/zitadel/zitadel/pull/11706 already reverted an unintended rename of the feature key to enable the management console to use the V2 API for user creation. It was now also discovered that the rename of the feature itself also broke existing (default) configurations. # How the Problems Are Solved Added a `mapstructure` tag on the instance feature to handle existing configs. # Additional Changes Removed unused `TokenExchange` from the default configuration. # Additional Context - relates to #11390 - relates to #11706 - requires backport to v4.x --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Marco A. <marco@zitadel.com>
6 days ago by Livio Spring
Succeeded
feat/support-standard-otel-vars
67434233 fix: revert feature key for configs back to ConsoleUseV2UserApi (#11928) # Which Problems Are Solved https://github.com/zitadel/zitadel/pull/11390 renamed "Console" to "Management Console". While https://github.com/zitadel/zitadel/pull/11706 already reverted an unintended rename of the feature key to enable the management console to use the V2 API for user creation. It was now also discovered that the rename of the feature itself also broke existing (default) configurations. # How the Problems Are Solved Added a `mapstructure` tag on the instance feature to handle existing configs. # Additional Changes Removed unused `TokenExchange` from the default configuration. # Additional Context - relates to #11390 - relates to #11706 - requires backport to v4.x --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Marco A. <marco@zitadel.com>
6 days ago by Livio Spring
Succeeded
main
21b28b56 fix: revert feature key for configs back to ConsoleUseV2UserApi (#11928) # Which Problems Are Solved https://github.com/zitadel/zitadel/pull/11390 renamed "Console" to "Management Console". While https://github.com/zitadel/zitadel/pull/11706 already reverted an unintended rename of the feature key to enable the management console to use the V2 API for user creation. It was now also discovered that the rename of the feature itself also broke existing (default) configurations. # How the Problems Are Solved Added a `mapstructure` tag on the instance feature to handle existing configs. # Additional Changes Removed unused `TokenExchange` from the default configuration. # Additional Context - relates to #11390 - relates to #11706 - requires backport to v4.x --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Marco A. <marco@zitadel.com>
6 days ago by Livio Spring
Succeeded
main
21b28b56 fix: revert feature key for configs back to ConsoleUseV2UserApi (#11928) # Which Problems Are Solved https://github.com/zitadel/zitadel/pull/11390 renamed "Console" to "Management Console". While https://github.com/zitadel/zitadel/pull/11706 already reverted an unintended rename of the feature key to enable the management console to use the V2 API for user creation. It was now also discovered that the rename of the feature itself also broke existing (default) configurations. # How the Problems Are Solved Added a `mapstructure` tag on the instance feature to handle existing configs. # Additional Changes Removed unused `TokenExchange` from the default configuration. # Additional Context - relates to #11390 - relates to #11706 - requires backport to v4.x --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Marco A. <marco@zitadel.com>
6 days ago by Livio Spring
Succeeded
main
21b28b56 fix: revert feature key for configs back to ConsoleUseV2UserApi (#11928) # Which Problems Are Solved https://github.com/zitadel/zitadel/pull/11390 renamed "Console" to "Management Console". While https://github.com/zitadel/zitadel/pull/11706 already reverted an unintended rename of the feature key to enable the management console to use the V2 API for user creation. It was now also discovered that the rename of the feature itself also broke existing (default) configurations. # How the Problems Are Solved Added a `mapstructure` tag on the instance feature to handle existing configs. # Additional Changes Removed unused `TokenExchange` from the default configuration. # Additional Context - relates to #11390 - relates to #11706 - requires backport to v4.x --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Marco A. <marco@zitadel.com>
6 days ago by Livio Spring
Failed
fix-org-setup-existence-check
b70de0be fix: revert feature key for configs back to ConsoleUseV2UserApi (#11928) # Which Problems Are Solved https://github.com/zitadel/zitadel/pull/11390 renamed "Console" to "Management Console". While https://github.com/zitadel/zitadel/pull/11706 already reverted an unintended rename of the feature key to enable the management console to use the V2 API for user creation. It was now also discovered that the rename of the feature itself also broke existing (default) configurations. # How the Problems Are Solved Added a `mapstructure` tag on the instance feature to handle existing configs. # Additional Changes Removed unused `TokenExchange` from the default configuration. # Additional Context - relates to #11390 - relates to #11706 - requires backport to v4.x --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Marco A. <marco@zitadel.com>
6 days ago by Livio Spring
Succeeded
main
21b28b56 fix: revert feature key for configs back to ConsoleUseV2UserApi (#11928) # Which Problems Are Solved https://github.com/zitadel/zitadel/pull/11390 renamed "Console" to "Management Console". While https://github.com/zitadel/zitadel/pull/11706 already reverted an unintended rename of the feature key to enable the management console to use the V2 API for user creation. It was now also discovered that the rename of the feature itself also broke existing (default) configurations. # How the Problems Are Solved Added a `mapstructure` tag on the instance feature to handle existing configs. # Additional Changes Removed unused `TokenExchange` from the default configuration. # Additional Context - relates to #11390 - relates to #11706 - requires backport to v4.x --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Marco A. <marco@zitadel.com>
6 days ago by Livio Spring
Succeeded
console-feature
a67c64ac fix: do not send init mails for admins on instance setup (#11744) # Which Problems Are Solved Currently when setting up an instance, for example from the customer portal through system api, an instance is created together with an administrator. If no admin user is specified the default user from the runtime configuration is automatically added. For the new onboarding, we can to create instances without prompting the user to set up a complete account right on start, but the current behavior of the API prevents this, resp. the created account would fallback to the default user or password. By providing an empty `password` field in the `owner_password` in the `AddInstanceRequest` or `huiman.password` in the `CreateInstanceRequest`, it's already possible to create an account without password. Until now this however ended up in an initial mail to be sent to the user to finalize their account setup. # How the Problems Are Solved We simply set the `allowInitMail` to false in the `AddHumanCommand` for setting up the admins. This will prevent an email to be sent out immediately and gives us the possibility to use the invite flow later on. # Additional Changes None # Additional Context - required for https://github.com/zitadel/website/issues/1611 - backport to v4.x
6 days ago by Livio Spring
Succeeded
feat-otp-email-challenge-rt-session
f3ff09b8 fix: do not send init mails for admins on instance setup (#11744) # Which Problems Are Solved Currently when setting up an instance, for example from the customer portal through system api, an instance is created together with an administrator. If no admin user is specified the default user from the runtime configuration is automatically added. For the new onboarding, we can to create instances without prompting the user to set up a complete account right on start, but the current behavior of the API prevents this, resp. the created account would fallback to the default user or password. By providing an empty `password` field in the `owner_password` in the `AddInstanceRequest` or `huiman.password` in the `CreateInstanceRequest`, it's already possible to create an account without password. Until now this however ended up in an initial mail to be sent to the user to finalize their account setup. # How the Problems Are Solved We simply set the `allowInitMail` to false in the `AddHumanCommand` for setting up the admins. This will prevent an email to be sent out immediately and gives us the possibility to use the invite flow later on. # Additional Changes None # Additional Context - required for https://github.com/zitadel/website/issues/1611 - backport to v4.x
6 days ago by Livio Spring
Succeeded
console-feature
a67c64ac Merge 967684ce7eed7d5ab22921843d520e55075034f3 into 0390e324e44f7b03a1be28ad9b50151e24b8c619
6 days ago by Livio Spring
Succeeded
main
0390e324 fix: do not send init mails for admins on instance setup (#11744) # Which Problems Are Solved Currently when setting up an instance, for example from the customer portal through system api, an instance is created together with an administrator. If no admin user is specified the default user from the runtime configuration is automatically added. For the new onboarding, we can to create instances without prompting the user to set up a complete account right on start, but the current behavior of the API prevents this, resp. the created account would fallback to the default user or password. By providing an empty `password` field in the `owner_password` in the `AddInstanceRequest` or `huiman.password` in the `CreateInstanceRequest`, it's already possible to create an account without password. Until now this however ended up in an initial mail to be sent to the user to finalize their account setup. # How the Problems Are Solved We simply set the `allowInitMail` to false in the `AddHumanCommand` for setting up the admins. This will prevent an email to be sent out immediately and gives us the possibility to use the invite flow later on. # Additional Changes None # Additional Context - required for https://github.com/zitadel/website/issues/1611 - backport to v4.x
6 days ago by Livio Spring
Succeeded
console-feature
101b48b8 Merge 87aef0cfab4360109fc999dc160a97a5fb38abe1 into b145f1c85a5bfe2672272d4f460da41c6f7c40a8
6 days ago by Livio Spring
Succeeded
instance-w/o-admin
47d7dbd6 Merge b26ecab8c3e5ec7244e4467d00e6744def297192 into b145f1c85a5bfe2672272d4f460da41c6f7c40a8
6 days ago by Livio Spring
Succeeded
console-feature
14ca7b8f update tests
6 days ago by Livio Spring