Rhi @Rameesa P ls check Login Form under Login Behavior and Security settings to "controls whether loginName supports both email and username."
This is for org, you can do the same for all orgs under the default settings, maybe Disabled Email Login
This is for org, you can do the same for all orgs under the default settings, maybe Disabled Email Login
Rcan you also check the Default Settings too?.
Rhi @Rameesa P thanks for the sreenshots, what version are you on rn?
also "ZITADEL UI shows that users there only have email listed as a login method."
can you pls share the screeshot here?
and finally can you verify your Domain Settings and if Login Name Pattern is unchecked?.
Thanks
also "ZITADEL UI shows that users there only have email listed as a login method."
can you pls share the screeshot here?
and finally can you verify your Domain Settings and if Login Name Pattern is unchecked?.
Thanks
Rthis page basically(screenshot below) . And below is my theory 
If its UNCHECKED
If its UNCHECKED
- Login names must be unique across ALL organizations in your ZITADEL instance.
- The
loginNamefor a user will be exactly what was entered as their username (e.g., "john.doe" or "john.doe@example.com"). - This is likely the state of the organization where login ONLY works with email. In this scenario, it's highly probable that when the users were created in that specific organization, their email address was used as their primary
.username- So, their
loginNameis their email address (e.g.,username: "user@example.com"). - The ZITADEL UI showing "users there only have email listed as a login method" strongly supports this. Their registered login name is the email.
- Since there isn't a separate, non-email "username" defined for them (like just "user"), trying to log in with "user" would fail.
- So, their
