<?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 application]]></title><description><![CDATA[A list of topics that have been tagged with application]]></description><link>https://fusionauth.io/community/forum/tags/application</link><generator>RSS for Node</generator><lastBuildDate>Mon, 16 Nov 2026 13:47:01 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/tags/application.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[How to share SSO session between two applications in the same tenant?]]></title><description><![CDATA[<p dir="auto">Yes, you need to create two separate applications within the same tenant in FusionAuth. Here's how to configure this:</p>
Configuration Steps


<p dir="auto"><strong>Create both applications in the same tenant</strong> - Users are scoped at the tenant level, so applications in the same tenant can share authentication state through FusionAuth's SSO session.</p>


<p dir="auto"><strong>Enable self-service registration on the second application</strong> - This ensures a seamless login experience. When a user navigates to the second application while already authenticated to the first, they will be automatically registered and logged in.</p>


How It Works

User logs into the first application at your registration URL to create their account. Make sure the rememberDevice parameter is true or checked. You can modify your theme to hardcode that value.
While that session is valid, they navigate to the second application's login URL
They are automatically registered and authenticated to the second application without manual intervention

<p dir="auto">The key to this working is that FusionAuth creates an SSO session at the tenant level when a user logs in and rememberDevice is checked. When the authenticated user tries to access the second application, FusionAuth recognizes the existing SSO session and automatically creates a registration for that user in the second application (when self-service registration is enabled).</p>
Password Reset Behavior
<p dir="auto">Because users are scoped at the tenant level, a password reset applies to all applications under that tenant. Users can utilize the password reset page for the first application and will be able to log in at the second application with the new password.</p>
Sharing Templates
<p dir="auto">Both applications can share the same theme and templates. Themes are assigned at the tenant level (though you can also assign application-specific themes if needed starting with FusionAuth 1.27+). This means you can configure one set of templates - including password reset, login, and user management pages - that will be used by both applications.</p>
Pre-creating User Accounts
<p dir="auto">If you create user accounts ahead of time, you can automatically include the registration for the second application when creating the users. This would mean adding that application to their registrations when you create the account initially using the <a href="https://fusionauth.io/docs/apis/registrations/create-a-user-and-registration-combined" rel="nofollow ugc">Create a User and Registration API</a>.</p>
Related Documentation

<a href="https://fusionauth.io/docs/lifecycle/authenticate-users/single-sign-on" rel="nofollow ugc">Implementing Single Sign-On</a> - Complete guide to configuring SSO between applications
<a href="https://fusionauth.io/docs/lifecycle/register-users/basic-registration-forms#self-service-registration-and-registrations" rel="nofollow ugc">Self-Service Registration</a> - How automatic registration works when SSO is enabled
<a href="https://fusionauth.io/docs/apis/registrations/create-a-user-registration-for-an-existing-user" rel="nofollow ugc">Create a User Registration API</a> - Programmatically register existing users to additional applications
<a href="https://fusionauth.io/blog/announcing-fusionauth-1-27#application-themes" rel="nofollow ugc">Application Themes</a> - Configure application-specific themes if needed
<a href="https://fusionauth.io/docs/customize/look-and-feel/" rel="nofollow ugc">Themes Documentation</a> - Customize and share login pages and templates across applications

]]></description><link>https://fusionauth.io/community/forum/topic/3254/how-to-share-sso-session-between-two-applications-in-the-same-tenant</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/3254/how-to-share-sso-session-between-two-applications-in-the-same-tenant</guid><dc:creator><![CDATA[FASupportBot]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Disable login to an application without deleting it]]></title><description><![CDATA[<p dir="auto">You have a couple of options.</p>

If you use the hosted login pages/authorization code grant, disabling all grants in the application settings page will prevent people from logging in.
If you use the login API and have customer-based API keys, you could turn on the 'require API key for login API' and then disable the customer's API key.
If you have the Enterprise plan, you could set up an <a href="https://fusionauth.io/docs/operate/secure/advanced-threat-detection#ip-access-control-lists" rel="nofollow ugc">IP ACL</a> for a unroutable IP range.

<p dir="auto">However, the easiest way to make sure an application cannot be logged into is to deactivate the application.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/3135/disable-login-to-an-application-without-deleting-it</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/3135/disable-login-to-an-application-without-deleting-it</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Application is blank on the login records]]></title><description><![CDATA[<p dir="auto">There are a couple different scenarios where a login record could have a blank application Id. Usually it is #1 or #2. It occurs in scenarios where the user can have a JWT/access token that does not have the application Id in it.</p>

If a user is not registered for the Application they are logging into
FusionAuth makes a login record when a user is created since FA makes a JWT upon user creation
If you use the Login API, you can log in without an App ID because you don't have to provide an application on the API call.

]]></description><link>https://fusionauth.io/community/forum/topic/3104/application-is-blank-on-the-login-records</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/3104/application-is-blank-on-the-login-records</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><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[FusionAuth not registering user in multiple Applications (GO-Client)]]></title><description><![CDATA[<p dir="auto">Solution:</p>
<p dir="auto"><a href="https://github.com/FusionAuth/go-client/issues/48" rel="nofollow ugc">https://github.com/FusionAuth/go-client/issues/48</a></p>
]]></description><link>https://fusionauth.io/community/forum/topic/1493/fusionauth-not-registering-user-in-multiple-applications-go-client</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/1493/fusionauth-not-registering-user-in-multiple-applications-go-client</guid><dc:creator><![CDATA[arihantverma52]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Link in Email verification not working first time]]></title><description><![CDATA[<p dir="auto">We have the exact same issue. If this was solved (hopefully) could you please provide a brief description on the fix?<br />
Thanks!</p>
]]></description><link>https://fusionauth.io/community/forum/topic/1406/link-in-email-verification-not-working-first-time</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/1406/link-in-email-verification-not-working-first-time</guid><dc:creator><![CDATA[skelsec]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Custom theme deployment between environments]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/114">@fred-fred</a> said in <a href="/community/forum/post/3982">Custom theme deployment between environments</a>:</p>
<blockquote>
<p dir="auto">It looks like we can transport with the API using Theme Update Endpoints and sharing environment API keys so one environment can see the next environment to copy the themes over.</p>
</blockquote>
<p dir="auto">Yes, that's what I'd recommend. You could have different API keys for each environment and have the script that promotes the theme pull the API key from a secrets store. Make sure you limit the API key to the themes endpoint.</p>
<p dir="auto">You also might be interested in this post: <a href="https://fusionauth.io/community/forum/topic/1306/parameterizing-themes">https://fusionauth.io/community/forum/topic/1306/parameterizing-themes</a> which indicates how you can have the same theme files point to different resources in staging/prod/dev/etc.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/1373/custom-theme-deployment-between-environments</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/1373/custom-theme-deployment-between-environments</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Can I temporarily disable logging into an application?]]></title><description><![CDATA[<p dir="auto">Yes, you can disable one or more applications.</p>
<p dir="auto">This operation can be reversed, and while an application is disabled, login requests to fail with a 400 error for all users.</p>
<p dir="auto">Navigate to "Applications -&gt; Deactivate (gray button)" to disable/deactivate an application.</p>
<p dir="auto">To re-enable it from the admin UI, you'll need to 'view inactive', which is the button next to the green '+' sign on the list applications page.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/818/can-i-temporarily-disable-logging-into-an-application</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/818/can-i-temporarily-disable-logging-into-an-application</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Custom themes for an application]]></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> This was delivered in 1.27.0</p>
]]></description><link>https://fusionauth.io/community/forum/topic/534/custom-themes-for-an-application</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/534/custom-themes-for-an-application</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[FusionAuth application id]]></title><description><![CDATA[<p dir="auto">Yes, it's the fusionauth application id, defined here: <a href="https://github.com/FusionAuth/fusionauth-java-client/blob/master/src/main/java/io/fusionauth/domain/Application.java" rel="nofollow ugc">https://github.com/FusionAuth/fusionauth-java-client/blob/master/src/main/java/io/fusionauth/domain/Application.java</a></p>
]]></description><link>https://fusionauth.io/community/forum/topic/427/fusionauth-application-id</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/427/fusionauth-application-id</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Search for users by application]]></title><description><![CDATA[<p dir="auto">You should be able to go the user's tab and then expand the 'advanced' section and select a given application.</p>
<p dir="auto">See this screenshot:</p>
<p dir="auto">user search with 'advanced' section expanded</p>
]]></description><link>https://fusionauth.io/community/forum/topic/391/search-for-users-by-application</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/391/search-for-users-by-application</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[How many applications and tenants can I have in FusionAuth?]]></title><description><![CDATA[<p dir="auto">Ah, yes, thanks for explaining.</p>


<p dir="auto">Yes</p>


<p dir="auto">You have two options</p>



use the API to integrate with the current login/reg flow with FusionAuth. This lets you keep your existing html pretty much untouched, you're just calling out to FusionAuth instead of the database.
remove them and use the FusionAuth provided pages with OIDC. This lets you use the theming and localization capabilities of FusionAuth, including super simple social signon.

<p dir="auto">It's your choice based on what your needs are, either way will work.</p>
<p dir="auto">I'd only recommend using SAML if you have an application which only supports SAML, not OIDC.</p>
<p dir="auto">You'll also want to make sure that when someone registers with one of your applications in FusionAuth, they register with all three. I'd probably use a webhook to ensure that.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/295/how-many-applications-and-tenants-can-i-have-in-fusionauth</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/295/how-many-applications-and-tenants-can-i-have-in-fusionauth</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[Is there a way to force users to use two factor authentication?]]></title><description><![CDATA[<p dir="auto">Not with a FusionAuth policy, but you could enforce it just by checking the user during login, as twoFactorEnabled is an attribute of the user.</p>
<p dir="auto">There's also this github issue which you may want to vote up: <a href="https://github.com/FusionAuth/fusionauth-issues/issues/763" rel="nofollow ugc">https://github.com/FusionAuth/fusionauth-issues/issues/763</a></p>
]]></description><link>https://fusionauth.io/community/forum/topic/268/is-there-a-way-to-force-users-to-use-two-factor-authentication</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/268/is-there-a-way-to-force-users-to-use-two-factor-authentication</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item><item><title><![CDATA[How do you assign a theme to an application?]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/114">@fred-fred</a></p>
<p dir="auto">Hiya,</p>
<p dir="auto">In addition to what <a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/56">@maciej-wisniowski</a> suggested, if you have a paid license you can now have application specific themes (one theme per application; if no application theme is specified, it defaults to the tenant).</p>
<p dir="auto">You can see how that works in the sandbox environment (<a href="http://sandbox.fusionauth.io" rel="nofollow ugc">sandbox.fusionauth.io</a>). I believe that feature landed in 1.27.0.</p>
<p dir="auto">You can buy a <a href="https://fusionauth.io/pricing/" rel="nofollow ugc">licensed edition here</a>.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/42/how-do-you-assign-a-theme-to-an-application</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/42/how-do-you-assign-a-theme-to-an-application</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>