Auth error Configuration locally (Next-Auth v5) (Docker)
I have error When i press on login button is not redirect to zitadel login
In the images you will find the details about the error and my setup in docker...
duplicate key value violates unique constraint "unique_constraints_pkey"
Use-case: SSO for clients using our company applications.
Environment: Self Hosting
Version: v3.1.0 / v3.3.2...
Microsoft Provider callback issue
When following the documentation to use Microsoft Provider
we got the following error:
Request Id: df84388e-b0a0-4e6e-ba56-c9e02a9f4400
Correlation Id: 961f6dfe-be9d-470e-a33b-06beb8553901
Timestamp: 2025-07-31T12:32:09Z...
This is regarding cockroachdb Migration to Postgres,
My setup is done with helmcharts with database cockraochdb, i am using zitadel mirror to migrate to cockroachdb to postgres,
i have using secure cockraochdb deployed with helmcharts, its done aks environment
I am doing like this , i have port-forward cockraochdb and postgresl both, ...
User invalid email (local host) (docker-compose)
I try to setup zitadel locally with docker and next-auth v5
But its every time i run the container the zitadel is failed run because of user email
This is the error...
How to troubleshoot issues regarding not finding user record on external authentication?
Currently we are using Zitadel v2.41.14. We have configured successfully EntraID SAML provider using this documentation https://zitadel.com/docs/guides/integrate/identity-providers/azure-ad-saml . On first login, it works fine, as the user gets created automatically.
However, when the user logs in again, it seems it doesn't find the matching identity provider record, so it tries to create it again automatically, but it fails because the record already exists. What could be wrong in my config? Or, is there a way or an specific log I can try to find to understand what is the root cause of this issue?...
**Subject: Issue Retrieving and Assigning Custom Project Roles via API**
ZITADEL distinguishes between:
Project Roles: These are the custom roles you define within a specific project (like "ADMIN1", "SUPPORT"). They are keys that represent a set of permissions relevant to your application's logic. You create these at management/v1/projects/{projectId}/roles.
Project Members / User Grants: This is where you assign a specific user (from your organization or a granted organization) one or more of these defined Project Roles for a given project. When a user is assigned a role in a project, it's essentially a "user grant."...
Microsoft IdP Login Fails: Missing given_name Causes Validation Error
Hello, I'm setting up Microsoft as an Identity Provider for my app using Zitadel. I followed all the documentation, and login is successful, but right after that, I run into this error:
[invalid_argument] invalid AddHumanUserRequest.Profile: embedded message failed validation | caused by: invalid SetHumanProfile.GivenName: value length must be between 1 and 200 runes, inclusive
Even though I have added given_name as a claim in the token configuration of my Azure App Registration, It seems like it might be missing or empty in the token being returned.
Can anyone help me identify why this might be happening or suggest a workaround? maybe creating an action to map name to given_name can fix this (not sure if possible)?...