<?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 registration]]></title><description><![CDATA[A list of topics that have been tagged with registration]]></description><link>https://fusionauth.io/community/forum/tags/registration</link><generator>RSS for Node</generator><lastBuildDate>Fri, 06 Mar 2026 20:49:29 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/tags/registration.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[allow users to register for any application but not create user accounts]]></title><description><![CDATA[<p dir="auto">This is possible in a couple of ways.</p>
<p dir="auto">First, to allow users to register for an application on login, you need to turn on self-service registration. <a href="https://fusionauth.io/docs/get-started/core-concepts/registrations#registrations-and-self-service-registration" rel="nofollow ugc">From the docs</a>:</p>
<blockquote>
<p dir="auto">When you enable self-service registration for an application and a user who does not have a registration for that application successfully logs in to that application, the user will automatically be registered for that application, and have a registration added.</p>
</blockquote>
<p dir="auto">Then the question becomes, how can you disable the hosted login pages self-service registration form?</p>
<p dir="auto">To do so, take the following steps:</p>

update your theme to remove the link to the "Don't have an account? Create one" link from any pages, including the login page. You can also remove all the content from the registration themed page and replace it with not implemented or similar. However, a sinister user may still be able to post to the register endpoint and create a user
if you are self-hosting, block access to the /register endpoint using a proxy
if you are not self-hosting, prevent self-service registration by adding an encrypted secret value to all user accounts you create via the API. Then, create <a href="https://fusionauth.io/docs/extend/code/lambdas/self-service-registration" rel="nofollow ugc">self-service registration validation lambda</a> which will examine the user object. If the user object comes through without the secret value, fail the registration. Otherwise allow it through because it is a user who has logged in.

<p dir="auto">The self-service lambda may not fire unless there are required fields on the registration form, but that behavior is undocumented and may change.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2916/allow-users-to-register-for-any-application-but-not-create-user-accounts</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2916/allow-users-to-register-for-any-application-but-not-create-user-accounts</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Unverified Behavior Setting Not Respected]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/3183">@ahcfrontdoor</a> I set up an application with the setting you are talking about and was allowed to register and proceed without any re-direction. Can you share a screen shot of your application registration tab. Please be sure to black out any sensitive information if necessary.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2752/unverified-behavior-setting-not-respected</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2752/unverified-behavior-setting-not-respected</guid><dc:creator><![CDATA[mark.robustelli]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Why does import user with Registration fail?]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/2884">@fusionauth-qhj5e</a> I have brought this up internally, for now we are considering adding a PR to make it more clear for users.</p>
<p dir="auto"><a href="https://github.com/FusionAuth/fusionauth-site/pull/2918" rel="nofollow ugc">https://github.com/FusionAuth/fusionauth-site/pull/2918</a></p>
]]></description><link>https://fusionauth.io/community/forum/topic/2630/why-does-import-user-with-registration-fail</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2630/why-does-import-user-with-registration-fail</guid><dc:creator><![CDATA[[[global:former-user]]]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Registering with an existing email]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/212">@harish_reddy</a> I just want to make sure I understand where you are coming from.  If you user signs up with an email address, you want the same response even if they are already signed up?  Can you please share some images of how you would like the flow to work?  I think this could cause problems and confusion the way I am thinking about it.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2484/registering-with-an-existing-email</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2484/registering-with-an-existing-email</guid><dc:creator><![CDATA[mark.robustelli]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[How to get populated user.data after user registraion.]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/1292">@muravyov-alexey</a> Thank you!</p>
]]></description><link>https://fusionauth.io/community/forum/topic/1443/how-to-get-populated-user-data-after-user-registraion</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/1443/how-to-get-populated-user-data-after-user-registraion</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Unable to invoke @ValidationMethod on the class [class io.fusionauth.app.action.oauth2.CompleteRegistrationAction]]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/727">@alessandrojcm</a>,</p>
<p dir="auto">Sounds good.  I have logged a <a href="https://github.com/FusionAuth/fusionauth-issues/issues/1255" rel="nofollow ugc">bug report</a>; we should have this one squashed soon!</p>
<p dir="auto">Thanks,<br />
Josh</p>
]]></description><link>https://fusionauth.io/community/forum/topic/1076/unable-to-invoke-validationmethod-on-the-class-class-io-fusionauth-app-action-oauth2-completeregistrationaction</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/1076/unable-to-invoke-validationmethod-on-the-class-class-io-fusionauth-app-action-oauth2-completeregistrationaction</guid><dc:creator><![CDATA[joshua]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[External validation of users on registration]]></title><description><![CDATA[<p dir="auto">You can use the user.create or the user.registration.create webhook to do something like this.</p>
<p dir="auto">If you enable these webhooks and configure the transaction to require the webhook to succeed, then you simply need to return a non-200 status code from the webhook to cause FusionAuth to fail this create.</p>
<p dir="auto"><a href="https://fusionauth.io/docs/v1/tech/events-webhooks/#tenant-settings" rel="nofollow ugc">https://fusionauth.io/docs/v1/tech/events-webhooks/#tenant-settings</a><br />
<a href="https://fusionauth.io/docs/v1/tech/events-webhooks/events/#user-create" rel="nofollow ugc">https://fusionauth.io/docs/v1/tech/events-webhooks/events/#user-create</a><br />
<a href="https://fusionauth.io/docs/v1/tech/events-webhooks/events/#user-registration-create" rel="nofollow ugc">https://fusionauth.io/docs/v1/tech/events-webhooks/events/#user-registration-create</a></p>
]]></description><link>https://fusionauth.io/community/forum/topic/982/external-validation-of-users-on-registration</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/982/external-validation-of-users-on-registration</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Lambda reconcile does not remove role from registration]]></title><description><![CDATA[<p dir="auto">Hi <a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/717">@tl-fa</a>,</p>
<p dir="auto">You can view our <a href="https://fusionauth.io/docs/v1/tech/core-concepts/roadmap/#overview" rel="nofollow ugc">Roadmap Guidance</a> regarding how features are implemented into FusionAuth.  A good snapshot of current development can be found <a href="https://github.com/FusionAuth/fusionauth-issues/projects/2" rel="nofollow ugc">here</a> as well.</p>
<p dir="auto">We will certainly update any related issue cards as development moves forward!</p>
<p dir="auto">Thanks!<br />
Josh</p>
]]></description><link>https://fusionauth.io/community/forum/topic/939/lambda-reconcile-does-not-remove-role-from-registration</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/939/lambda-reconcile-does-not-remove-role-from-registration</guid><dc:creator><![CDATA[joshua]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Existing users are registered for an application without seeing the registration form]]></title><description><![CDATA[<p dir="auto">Yes, if self service registration is enabled (which is set on an application by application basis) and a user who is already logged in to FusionAuth tries to register for such an application, FusionAuth will automatically register them for the app. It also checks that all required profile information is filled out, which is why adding the required field displays the registration form.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/844/existing-users-are-registered-for-an-application-without-seeing-the-registration-form</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/844/existing-users-are-registered-for-an-application-without-seeing-the-registration-form</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Advanced reporting, slicing and dicing by user and application and login&#x2F;registration]]></title><description><![CDATA[<p dir="auto">This functionality doesn't exist in the FusionAuth admin screens, please feel free to <a href="https://github.com/fusionauth/fusionauth-issues/issues" rel="nofollow ugc">file an issue with a detailed use case</a> if you feel it should.</p>
<p dir="auto">For registrations, you can look at the date the application registration was created using the <a href="https://fusionauth.io/docs/v1/tech/apis/users/#search-for-users" rel="nofollow ugc">User Search API</a>. You'll probably want to use a date range.</p>
<p dir="auto">For logins, you can review and search all login records by going to "System -&gt; Login Records". However, one could build something with more granularity using the FusionAuth APIs.</p>
<p dir="auto"><a href="https://fusionauth.io/docs/v1/tech/apis/login/#search-login-records" rel="nofollow ugc">This API documents how to pull down the log in data for a given date range</a>. This doesn't include the full user object, but does include the user id. From there you could use the user api to pull down the entire user object.</p>
<p dir="auto">Also, please note that login records may be deleted after a certain period of time, based on your system settings. This deletion is controlled in the admin UI, under "Settings -&gt; System -&gt; Advanced -&gt; Login record settings" and would impact your ability to query login data in the past if enabled.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/817/advanced-reporting-slicing-and-dicing-by-user-and-application-and-login-registration</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/817/advanced-reporting-slicing-and-dicing-by-user-and-application-and-login-registration</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[403 error when registering with Apple]]></title><description><![CDATA[<p dir="auto">Yes, just confirmed the fact that this is a Safari only issue. Only Safari seems to be doing this, we don’t return a 403 so this must a CORS failure. Perhaps Apple is sending additional headers on the request when using Safari that need to be accounted for in the Allowed headers.</p>
<p dir="auto">I added GET to the allowed methods for CORS and it works that seems to allow it to work in Safari. Please test and let me know.</p>
<p dir="auto">The redirect workflow looks to be different in Safari when using native controls vs Chrome or other browsers.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/699/403-error-when-registering-with-apple</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/699/403-error-when-registering-with-apple</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Dynamic Client Registration support]]></title><description><![CDATA[<p dir="auto"><a href="https://github.com/FusionAuth/fusionauth-issues/issues/1125" rel="nofollow ugc">Please see this issue</a> for updates on this functionality. Vote for it if this is important to you.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/511/dynamic-client-registration-support</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/511/dynamic-client-registration-support</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Registration email is not sent]]></title><description><![CDATA[<p dir="auto">Hi, I have the same problem here. The tenant's SMTP setting are correct and test emails are successfully delivered. I'm evaluating the FusionAuth right now and often delete/re-register users with the same emails.  Verification emails are delivered to all users but one. The only thing that distinguish the problem user from the others is the fact I initially registered him via Facebook identity provider, so his email was automatically verified. After that I deleted the user and trying to register with just email (not Facebook). And emails are not delivered. Manually sent SMTP test emails to that address also delivered successfully. I hope this help to investigate.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/406/registration-email-is-not-sent</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/406/registration-email-is-not-sent</guid><dc:creator><![CDATA[ishuvalov]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Can you register a user to an application at the same time as you create them]]></title><description><![CDATA[<p dir="auto">Is this what you are looking for?: <a href="https://fusionauth.io/docs/v1/tech/apis/registrations#create-a-user-and-registration-combined" rel="nofollow ugc">https://fusionauth.io/docs/v1/tech/apis/registrations#create-a-user-and-registration-combined</a></p>
<p dir="auto">That API does return a token as of v1.17.0.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/402/can-you-register-a-user-to-an-application-at-the-same-time-as-you-create-them</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/402/can-you-register-a-user-to-an-application-at-the-same-time-as-you-create-them</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Password validation rules]]></title><description><![CDATA[<p dir="auto">Our validation takes in inverse approach. The setting is actually to require a non-alphanumeric character.  So any character that is not alphabetic, or a digit, will satisfy this requirement.</p>
<p dir="auto">There is not a fixed set of symbols as this would reduce the password entropy, which is generally a bad idea.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/371/password-validation-rules</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/371/password-validation-rules</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>