<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with username]]></title><description><![CDATA[A list of topics that have been tagged with username]]></description><link>https://fusionauth.io/community/forum/tags/username</link><generator>RSS for Node</generator><lastBuildDate>Wed, 12 Aug 2026 09:30:05 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/tags/username.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[Username as the LoginID for forgot password workflow]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/2403">@david-4</a> , Is this what you are looking for? <a href="https://fusionauth.io/docs/customize/email-and-messages/templates-replacement-variables#using-replacement-variables" rel="nofollow ugc">Using Replacement Variables</a></p>
]]></description><link>https://fusionauth.io/community/forum/topic/2681/username-as-the-loginid-for-forgot-password-workflow</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2681/username-as-the-loginid-for-forgot-password-workflow</guid><dc:creator><![CDATA[mark.robustelli]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Email or phone number to login?]]></title><description><![CDATA[<p dir="auto">Yes. That’s how it currently works.</p>
<p dir="auto">We have on the roadmap a more flexible identity system but don't have a current timeline for implementation. Here's the tracking issue: <a href="https://github.com/FusionAuth/fusionauth-issues/issues/1" rel="nofollow ugc">https://github.com/FusionAuth/fusionauth-issues/issues/1</a></p>
]]></description><link>https://fusionauth.io/community/forum/topic/1221/email-or-phone-number-to-login</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/1221/email-or-phone-number-to-login</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Unique usernames but not unique emails]]></title><description><![CDATA[<p dir="auto">I tried to specify both username and email and I got this error:</p>
{
  statusCode: 400,
  exception: {
    fieldErrors: {
      'user.email': [
        {
          code: '[blank]user.email',
          message: 'You must specify either the [user.email] or [user.username] property. If you are emailing the user you must specify the [user.email].'
        }
      ],
      'user.username': [
        {
          code: '[blank]user.username',
          message: 'You must specify either the [user.email] or [user.username] property. If you are emailing the user you must specify the [user.email].'
        }
      ]
    },
    generalErrors: []
  }
}

<p dir="auto">So basically I guess my best bet is to manually enforce uniqueness of username in my backend. But it could have been less cumbersome if I could delegate it to FusionAuth.</p>
<p dir="auto">I guess what I am trying to emphasis here is the fact that just by saving username in user.data we will be able to have both username and email but applying rules such as uniqueness would require more manual labor. Cannot we just tell FusionAuth to make sure that user.data.username should be unique in that app or tenant?</p>
Side note: Since my question is deviating from the OP I'll create a new post and reference this one.
]]></description><link>https://fusionauth.io/community/forum/topic/1032/unique-usernames-but-not-unique-emails</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/1032/unique-usernames-but-not-unique-emails</guid><dc:creator><![CDATA[kasir-barati]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[username search against the database?]]></title><description><![CDATA[<p dir="auto">The user and registration may have a username field. The username field on the user is the one that can be used to login. In general you will want to use the <a href="https://fusionauth.io/docs/v1/tech/apis/users/#search-for-users" rel="nofollow ugc">Search API</a> for those types of queries rather than directly accessing the database.</p>
<p dir="auto">The reason is because the API is documented and stable, and the database is undocumented and may change.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/1024/username-search-against-the-database</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/1024/username-search-against-the-database</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Can I have users login with either a username and email address, or do I have to pick one or the other?]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/20">@dan</a> I was trying to use the standard register interface from fusion. If I check that I want to use "username" for example, the registration form removes the email option. To circumvent and get both email and username I had to create my own register form.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/296/can-i-have-users-login-with-either-a-username-and-email-address-or-do-i-have-to-pick-one-or-the-other</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/296/can-i-have-users-login-with-either-a-username-and-email-address-or-do-i-have-to-pick-one-or-the-other</guid><dc:creator><![CDATA[titogarrido]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>