<?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[Popular Topics]]></title><description><![CDATA[A list of topics that are sorted by post count]]></description><link>https://fusionauth.io/community/forum/popular/weekly</link><generator>RSS for Node</generator><lastBuildDate>Tue, 17 Nov 2026 06:53:49 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/popular/weekly.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 16 Nov 2026 20:44:40 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Permify Pull Request]]></title><description><![CDATA[<p dir="auto">Hi <a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/3902">@jack</a> thanks for filing the issue.</p>
<p dir="auto">We have a bug triage process internally and I'll make sure it gets in there, reviewed and prioritized.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/3394/permify-pull-request</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/3394/permify-pull-request</guid><dc:creator><![CDATA[dan]]></dc:creator><pubDate>Mon, 16 Nov 2026 20:44:40 GMT</pubDate></item><item><title><![CDATA[P2&#x2F;Sev2]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/3898">@paakhi-iyer</a></p>
<p dir="auto">GET /api/jwt/issue authenticates with a JWT, not an API key. It returns 401 if the Authorization header is missing or invalid, or if the access token is expired.</p>
<p dir="auto">I did find some changes that are within your version range of changes:</p>


<p dir="auto">1.60.0 token validation changes: Some existing, unexpired access or ID tokens may no longer be considered valid by FusionAuth. The gty and use claims moved from the JWT header to the body. New reserved claims were added, so lambdas that modify them need review.</p>


<p dir="auto">Endpoint use enforcement (1.60.x): FusionAuth now ensures endpoints only accept tokens suited to their intended use. A GitHub issue showed a token from the Login API being rejected by /oauth2/userinfo with "The token is not suitable for the requested use."</p>


<p dir="auto">1.69.0 key verification tightening: JWT verification is now strictly scoped to configured keys. If you rotated signing keys recently, tokens signed by an older key will fail unless that key is added to the tenant or application's verification key lists (accessTokenVerificationKeyIds and idTokenVerificationKeyIds). This is the most likely candidate if your 401s began right after the upgrade and you rotate keys. (<a href="https://fusionauth.io/docs/update/update-guides/1-69-0?utm_source=kapa#required-key-configuration-updates" rel="nofollow ugc">1.69.0 Guide</a>)</p>


<p dir="auto">Suggested checks</p>

Look in Key Master and your tenant and application JWT settings. Confirm every key that still signs valid tokens is listed in the verification key fields.
Check whether the 401 callers are sending expired tokens or an API key instead of a JWT.
Check whether any lambdas add, remove or modify gty, use, tty or auth_time claims.
Check whether the failing tokens were issued before the upgrade, since some unexpired tokens may now be invalid. Refreshing the token should resolve that.

]]></description><link>https://fusionauth.io/community/forum/topic/3390/p2-sev2</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/3390/p2-sev2</guid><dc:creator><![CDATA[mark.robustelli]]></dc:creator><pubDate>Thu, 12 Nov 2026 11:35:22 GMT</pubDate></item><item><title><![CDATA[Is 1.68.0 affected by the account-takeover vulnerability fixed in 1.69.2?]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/3901">@scott-m1dtya</a> Which issue are you talking about specifically. I don't think FusionAuth lists what versions an issue was introduced. Upgrading to the latest version is definitely the way to go.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/3391/is-1-68-0-affected-by-the-account-takeover-vulnerability-fixed-in-1-69-2</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/3391/is-1-68-0-affected-by-the-account-takeover-vulnerability-fixed-in-1-69-2</guid><dc:creator><![CDATA[mark.robustelli]]></dc:creator><pubDate>Fri, 13 Nov 2026 16:05:05 GMT</pubDate></item><item><title><![CDATA[How to perform load testing on FusionAuth for spiky traffic patterns?]]></title><description><![CDATA[<p dir="auto">Load testing FusionAuth typically involves using a modern tool like <a href="https://k6.io/" rel="nofollow ugc">k6</a> to simulate your expected traffic patterns. Here's the general approach:</p>


<p dir="auto"><strong>Use k6 or other HTTP-capable load testing tools</strong>: While k6 is a good modern option, FusionAuth can be load tested with any HTTP-capable load testing tool such as <a href="https://gatling.io/" rel="nofollow ugc">Gatling</a>, <a href="https://jmeter.apache.org/" rel="nofollow ugc">JMeter</a>, or <a href="https://github.com/locustio/locust" rel="nofollow ugc">Locust</a>. FusionAuth also provides an <a href="https://github.com/FusionAuth/fusionauth-load-tests/" rel="nofollow ugc">open source load testing repository</a> with pre-built scenarios including creating tenants and applications, registering users, logging users in via the Login API, and full Authorization Code grant flows.</p>


<p dir="auto"><strong>Profile your traffic</strong>: Use your load testing tool to determine what your actual traffic patterns will look like, especially accounting for your spiky demand. This helps you understand the load FusionAuth will need to handle. Look beyond just averages—also check the <strong>p95 (95th percentile)</strong> response time to understand the experience of your slowest users.</p>


<p dir="auto"><strong>Test in a production-like environment</strong>: It's critical to load test against an environment that mirrors your expected production setup. If you're using FusionAuth Cloud, the Basic Cloud tier (single node running FusionAuth, Elasticsearch, and PostgreSQL together) is not representative and not recommended for load testing. Instead, use a <strong>Business Cloud or High-Availability plan</strong> for meaningful load testing. You can spin up an HA instance, run your tests, and tear it down—you'll only be charged for the time it's running.</p>


<p dir="auto"><strong>Notify FusionAuth if testing on Cloud</strong>: If you're load testing on FusionAuth Cloud, open a support ticket to let the team know when you plan to stress test, as they monitor CPU and other metrics.</p>


<p dir="auto"><strong>Monitor the right components</strong>: Performance bottlenecks are typically the <strong>database</strong> or <strong>CPU nodes</strong>. Both logins and user creation are CPU-intensive due to password hashing. If testing a multi-node system behind a load balancer, disable sticky sessions as they are not required for FusionAuth.</p>


<p dir="auto"><strong>IP allowlisting considerations</strong>: If you're using FusionAuth Cloud, you may need to consider IP allowlisting depending on your security configuration. FusionAuth Cloud has protections in place to prevent DoS attacks and keep services running smoothly.</p>


<p dir="auto">The specific approach can vary based on your exact traffic patterns and requirements, but these are the key components most customers use when load testing FusionAuth.</p>
Related Documentation

<a href="https://fusionauth.io/docs/cloud/operate/load-test" rel="nofollow ugc">Load Test Documentation</a> - Comprehensive guide on load testing FusionAuth, including tool recommendations and best practices
<a href="https://github.com/FusionAuth/fusionauth-load-tests/" rel="nofollow ugc">FusionAuth Load Tests GitHub Repository</a> - Open source load testing scripts with pre-built scenarios
<a href="https://fusionauth.io/articles/gaming-entertainment/best-practices-spiky-registration" rel="nofollow ugc">Handling Spiky Game Traffic: Registration &amp; Autoscaling Best Practices</a> - Specific guidance for handling spiky traffic patterns during high-demand scenarios
<a href="https://fusionauth.io/docs/cloud/reference/high-availability" rel="nofollow ugc">FusionAuth Cloud High Availability Architecture</a> - Details on HA deployment options for production-like testing
<a href="https://fusionauth.io/docs/cloud/operate/security" rel="nofollow ugc">FusionAuth Cloud Security</a> - Information about Cloud security protections and rate limiting
<a href="https://fusionauth.io/docs/deploy/troubleshoot/troubleshooting#troubleshooting-performance" rel="nofollow ugc">Troubleshooting Performance</a> - Guide for troubleshooting performance issues
<a href="https://fusionauth.io/articles/ciam/making-sure-your-auth-system-scales" rel="nofollow ugc">Scaling Your Auth - Best Practices for Performance and Security</a> - General guidance on scaling authentication systems

]]></description><link>https://fusionauth.io/community/forum/topic/3360/how-to-perform-load-testing-on-fusionauth-for-spiky-traffic-patterns</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/3360/how-to-perform-load-testing-on-fusionauth-for-spiky-traffic-patterns</guid><dc:creator><![CDATA[FASupportBot]]></dc:creator><pubDate>Thu, 12 Nov 2026 18:16:05 GMT</pubDate></item><item><title><![CDATA[Can I reuse the same FusionAuth license key across dev, staging, and production?]]></title><description><![CDATA[<p dir="auto">Yes, you can use your FusionAuth licenses across multiple environments, but you should use the appropriate license type for each:</p>
License Structure
<p dir="auto">In your account portal at <a href="http://account.fusionauth.io" rel="nofollow ugc">account.fusionauth.io</a>, you should see <strong>two licenses</strong>:</p>

<strong>Production License</strong> — use this for your production environment only
<strong>Non-Production License</strong> — use this for your dev and staging environments

Best Practice

Deploy the <strong>Non-Production license</strong> to your dev and staging instances
Deploy the <strong>Production license</strong> to your production instance

<p dir="auto">Both licenses can be active simultaneously across different deployments without conflict. The license key itself is tied to your account and does not interfere with your managed FusionAuth Cloud setup when used in self-hosted deployments.</p>
Important Notes


<p dir="auto"><strong>The non-production license can be used across as many non-production environments as you need</strong> — dev, staging, QA, UAT, CI/CD, or even individual developer local instances. There's no limit on the number of instances using the non-production key.</p>


<p dir="auto"><strong>Do not use the production license on non-production environments</strong> — this would cause test logins to count toward your Monthly Active Users (MAU) and affect your billing.</p>


<p dir="auto"><strong>License costs are not based on the number of instances</strong> — whether you have 1, 2, or 100 instances, the license cost is related only to your plan tier and MAU count.</p>


<p dir="auto"><strong>Using self-hosted licenses won't affect your FusionAuth Cloud deployment</strong> — the licenses operate independently, so activating your license keys on self-hosted instances will not disrupt your existing managed environment.</p>


Related Documentation

<a href="https://fusionauth.io/docs/concepts/plans-and-limits/licensing" rel="nofollow ugc">Licensing Documentation</a> — Overview of FusionAuth licensing concepts
<a href="https://fusionauth.io/license-faq#i-have-a-paid-license-for-an-essential-plan-do-i-need-a-license-key-for-my-development-qa-uat-servers-to-access-the-essential-features" rel="nofollow ugc">License FAQ: Non-Production Licenses</a> — Details on using licenses for dev/QA/UAT servers
<a href="https://fusionauth.io/license-faq#if-i-have-a-licensed-plan-does-it-matter-how-many-deployments-a-license-is-installed-on-does-the-license-cost-change-based-on-whether-i-have-1-2-or-100-instances" rel="nofollow ugc">License FAQ: Multiple Deployments</a> — How license costs work with multiple instances
<a href="https://fusionauth.io/docs/cloud/account/#portal-areas" rel="nofollow ugc">Account Portal Documentation</a> — Where to find your license keys
<a href="https://fusionauth.io/docs/cloud/cloud-vs-self-hosted" rel="nofollow ugc">Cloud vs Self-Hosted</a> — Comparison of hosting options

]]></description><link>https://fusionauth.io/community/forum/topic/3358/can-i-reuse-the-same-fusionauth-license-key-across-dev-staging-and-production</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/3358/can-i-reuse-the-same-fusionauth-license-key-across-dev-staging-and-production</guid><dc:creator><![CDATA[FASupportBot]]></dc:creator><pubDate>Thu, 12 Nov 2026 16:26:28 GMT</pubDate></item><item><title><![CDATA[Why is &#96;act&#96; claim now reserved in 1.70.0? Lambda silently fails with no warning]]></title><description><![CDATA[<p dir="auto">The act claim was reserved in FusionAuth 1.70.0 because it is defined in <a href="https://datatracker.ietf.org/doc/html/rfc8693#section-4.1" rel="nofollow ugc">RFC 8693 (OAuth 2.0 Token Exchange)</a> as a standard claim representing the "actor" in delegated token scenarios. FusionAuth began enforcing this reservation to ensure compliance with the RFC and prevent conflicts with the claim's intended usage in token exchange flows.</p>
Why This Is Classified as Minor
<p dir="auto">FusionAuth follows semantic versioning, and this change was classified as minor rather than breaking because:</p>

The act claim is a <strong>standardized RFC claim</strong> with a specific defined purpose
Using non-standard values in RFC-defined claims can cause interoperability issues with other OAuth/OIDC systems
The change aligns FusionAuth's behavior with industry standards

<p dir="auto">However, the lack of logging when a reserved claim is silently discarded is a valid concern and makes troubleshooting difficult.</p>
Recommended Solutions
1. Use a Custom Claim Namespace
<p dir="auto">Instead of using act directly, use a namespaced custom claim that won't conflict with RFC-defined claims:</p>
// In your JWT populate lambda
jwt['https://yourapp.com/actor'] = 'your-actor-id';

<p dir="auto">This approach is standard practice in OAuth/OIDC and prevents future collisions with reserved claims.</p>
2. Use applicationId or Other Non-Reserved Claims
<p dir="auto">If the actor represents an application or service account, consider using the built-in applicationId claim or another custom claim that describes your specific use case (e.g., actorId, serviceAccountId).</p>
Why Reserved Claims Cannot Be Overridden
<p dir="auto">Reserved claims like act, sub, iss, aud, etc., are protected because they have specific meanings defined by RFCs and must maintain consistent behavior for:</p>

<strong>Interoperability</strong>: Other systems expect these claims to have specific formats and meanings
<strong>Security</strong>: Claims like iss and aud are critical for token validation and cannot be arbitrarily changed
<strong>Standards Compliance</strong>: FusionAuth aims to be a standards-compliant identity provider

Migration Path
<p dir="auto">If you're currently using act in production:</p>

Update your JWT populate lambda to use a namespaced custom claim
Update your application to read from the new claim name
Test thoroughly in a non-production environment before upgrading

<p dir="auto">If you need to maintain backward compatibility during migration, you could temporarily set both claims in your lambda (the custom namespaced one and attempt to set act, knowing it will be discarded) and update your application to check for both, prioritizing the custom claim.</p>

Related Documentation

<a href="https://fusionauth.io/docs/lambdas/tokens/jwt-populate" rel="nofollow ugc">JWT Populate Lambda</a> - Documentation on customizing JWT claims with lambdas
<a href="https://fusionauth.io/docs/lambdas/tokens/client-credentials-jwt-populate" rel="nofollow ugc">Client Credentials JWT Populate Lambda</a> - Documentation for lambdas in the Client Credentials grant
<a href="https://fusionauth.io/docs/authorization/token-exchange" rel="nofollow ugc">OAuth Token Exchange (RFC 8693)</a> - FusionAuth's implementation of RFC 8693, which defines the act claim
<a href="https://fusionauth.io/docs/release-notes#version-1-70-0" rel="nofollow ugc">FusionAuth 1.70.0 Release Notes</a> - Release notes for version 1.70.0
<a href="https://fusionauth.io/blog/announcing-fusionauth-1-70" rel="nofollow ugc">FusionAuth 1.70 Announcement: Token Exchange</a> - Blog post explaining the new token exchange feature and scoped delegation
<a href="https://github.com/FusionAuth/fusionauth-issues/issues/1721" rel="nofollow ugc">GitHub Issue #1721: JWT claim overriding, namespacing or the ability to unreserve claims</a> - Open issue discussing the ability to override or unreserve claims

Additional Context on Reserved Claims
<p dir="auto">As of FusionAuth 1.70.0, the following claims are reserved in <strong>JWT Populate Lambdas</strong> and cannot be modified:</p>

act (added in 1.70.0)
amr
auth_time
authenticationType
cnf
fa_uid
gty
iat
sub
tid
tty

<p dir="auto">Note: The exp claim can be <strong>lowered</strong> (shortened) but not extended or removed.</p>
<p dir="auto">For other lambda types (Client Credentials, UserInfo, Token Exchange), different sets of reserved claims apply. Always use namespaced custom claims (e.g., https://example.com/my-claim) to avoid conflicts with current or future reserved claims.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/3357/why-is-act-claim-now-reserved-in-1-70-0-lambda-silently-fails-with-no-warning</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/3357/why-is-act-claim-now-reserved-in-1-70-0-lambda-silently-fails-with-no-warning</guid><dc:creator><![CDATA[FASupportBot]]></dc:creator><pubDate>Tue, 10 Nov 2026 19:25:20 GMT</pubDate></item><item><title><![CDATA[403 on the post-login passkey offer when re-authentication is enabled only by an application override]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/3896">@pragnesh-nonghanvadra</a> If you can share your configuration settings and reproducible steps, i will try to go through it.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/3352/403-on-the-post-login-passkey-offer-when-re-authentication-is-enabled-only-by-an-application-override</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/3352/403-on-the-post-login-passkey-offer-when-re-authentication-is-enabled-only-by-an-application-override</guid><dc:creator><![CDATA[mark.robustelli]]></dc:creator><pubDate>Tue, 03 Nov 2026 09:37:20 GMT</pubDate></item><item><title><![CDATA[Can&#x27;t connect to web interface.]]></title><description><![CDATA[<p dir="auto">It looks like Elasticsearch may be causing the main issue since the container keeps restarting and consuming a high amount of CPU. I would recommend checking the Elasticsearch logs using docker logs ubuntu_search_1 and verifying that your server has enough RAM and CPU resources. Also, make sure Elasticsearch is healthy before troubleshooting FusionAuth connectivity. Since localhost:9011 returns a 302 redirect to /login, FusionAuth appears to be responding locally. Checking your firewall and cloud security group rules for port 9011 would also be a good next step. Hope this helps!</p>
]]></description><link>https://fusionauth.io/community/forum/topic/697/can-t-connect-to-web-interface</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/697/can-t-connect-to-web-interface</guid><dc:creator><![CDATA[ahsankhanbalcoh]]></dc:creator><pubDate>Mon, 28 Dec 2020 16:35:07 GMT</pubDate></item></channel></rss>