I can not set my instance settings to require a org domain suffix on all usernames
I get the error "User already exists (V3-DKcYh)" but I only have a single organization that already has suffixes enabled. How can I find that ghost user that is blocking this setting?
(see also: https://discord.com/channels/927474939156643850/1283210322810765343/1283210322810765343)
4 Replies
Hi @Manuel, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question.
Answer
I wasn't able to find a direct answer, here are some relevant sources:
1. ZITADEL Organizations :
Explains how ZITADEL handles usernames, org domain suffixes, and describes the effect of enabling the "user loginname must contain orgdomain" setting, including how usernames are generated and displayed. 2. [Bug]: User already exists error for external IDP login when checking for existing username :
Describes a scenario where username uniqueness and suffix handling can result in a "User already exists" error, even when domain suffixes are enabled, especially involving external identity providers. Feel free to tag @Ask Inkeep with additional questions.
Explains how ZITADEL handles usernames, org domain suffixes, and describes the effect of enabling the "user loginname must contain orgdomain" setting, including how usernames are generated and displayed. 2. [Bug]: User already exists error for external IDP login when checking for existing username :
Describes a scenario where username uniqueness and suffix handling can result in a "User already exists" error, even when domain suffixes are enabled, especially involving external identity providers. Feel free to tag @Ask Inkeep with additional questions.
I had a similar experience with orphaned records, see https://discord.com/channels/927474939156643850/1404888964892196915
Sadly there is nothing in
eventstore.unique_constraints that would explain the error, I found some names of deleted users, but none where duplicartes, I deleted all of them and still get the errorHello @Manuel apologies for the delay, have you tried upgrading to the latest version? There was a bug related to this issue that has been fixed. Thanks!