Mover server
Upgrade from 2.70.x to 2.71.x fails with migration errors
time="2025-03-28T17:41:50Z" level=info msg="starting migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:66" name=52_idp_templates6_ldap2
time="2025-03-28T17:41:50Z" level=error msg="migration failed" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:68" error="ERROR: relation \"idp_templates6_ldap2\" already exists (SQLSTATE 42P07)" name=52_idp_templates6_ldap2
time="2025-03-28T17:41:50Z" level=fatal msg="migration failed" caller="/home/runner/work/zitadel/zitadel/cmd/setup/setup.go:304" code=42P07 detail= error="ERROR: relation \"idp_templates6_ldap2\" already exists (SQLSTATE 42P07)" hint= message="relation \"idp_templates6_ldap2\" already exists" name=52_idp_templates6_ldap2 severity=ERROR
time="2025-03-28T17:41:50Z" level=info msg="starting migration" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:66" name=52_idp_templates6_ldap2
time="2025-03-28T17:41:50Z" level=error msg="migration failed" caller="/home/runner/work/zitadel/zitadel/internal/migration/migration.go:68" error="ERROR: relation \"idp_templates6_ldap2\" already exists (SQLSTATE 42P07)" name=52_idp_templates6_ldap2
time="2025-03-28T17:41:50Z" level=fatal msg="migration failed" caller="/home/runner/work/zitadel/zitadel/cmd/setup/setup.go:304" code=42P07 detail= error="ERROR: relation \"idp_templates6_ldap2\" already exists (SQLSTATE 42P07)" hint= message="relation \"idp_templates6_ldap2\" already exists" name=52_idp_templates6_ldap2 severity=ERROR
Automating Zitadel Configuration Without Manual UI Interaction or API Calls
Document updating process of Zitadel
Org Owner cannot see all users
"UNABLE_TO_VERIFY_LEAF_SIGNATURE" Error 403 Forbidden

Best Practices for Managing Public Domains in a B2B Organization Model
Entra SAML connect existing Zitadel accounts

Zitadel TypeScript login: Issues Enabling HTTP/2 for gRPC with Zitadel in K8S (ALB Ingress)
zitadel-typescript-login), but we’ve run into an issue with enabling HTTP/2 support while keeping compatibility with other services.
Our Setup...User metadata does not appear in the token

panic: runtime error: invalid memory address or nil pointer dereference

Revoking Active Sessions and Tokens
Looking for Help Setting Up Zitadel
Zitadel Fails DB Migration
Handling of deleted users
Access / refresh tokens
Fetch a List of users in a WebApp
Refresh token working, but still getting logged out!?
signInSilent which works when I set the ttl on the access token to 1 minute for example. So I thought everything is great, but when I set the access token ttl to 1 hour and the refresh token ttl to 31 days I would expect the user to have to login once a month. However the next day I'm forced to login again.
I don't understand why this is happening and I'm wondering if it has something to do with Zitadel itself??...