FusionAuth
    • Home
    • Categories
    • Recent
    • Popular
    • Pricing
    • Contact us
    • Docs
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics
    • All categories
    • J

      Unsolved Permify Pull Request

      Q&A
      • • • jack
      3
      0
      Votes
      3
      Posts
      183
      Views

      J

      @dan excellent. thank you

    • A

      Unsolved 403 calling Hosted Backend /app/refresh API

      Q&A
      • • • andrzej.taramina
      3
      0
      Votes
      3
      Posts
      392
      Views

      A

      @bryan-robinson

      I'm getting the 4503 even though I'm running the caller and FusionAuth on localhost for dev testing purposes. The caller is on localhost:8080 and FA is on localhost:9011.

      According to the documentation for app/refresh, this should work.

      Any ideas?

    • A

      Unsolved VueJS SDK call to app/me endpoint failing with 401 after upgrade to latest version of FusionAuth

      Q&A
      • • • andrzej.taramina
      3
      0
      Votes
      3
      Posts
      356
      Views

      A

      @bryan-robinson

      We are not using DPoP at all, and the app/me call is being made transparently by the FusionAuth Vue SDK, so is not something we can change. That is the default when setting up the VueJS SDK.

      I've isolated this to the upgrade to 1.60.0. It has the issue. 1.59.1 works fine.

      I suspect it's due to the new tty claim that is included in the at and idt tokens, which did not exist before.

      The external JWT reconcile API only returns at and rt tokens. It does not return an idt. So we were setting the at value for the idt cookie. But now that the two tokens can be differentiated, I suspect that this causes the issue.

      Was trying to use the Hosted Backend app/refresh API to get refreshed tokens, including an idt, but that is returning a 403-Forbidden for some reason. Documentation on what is required for that API call is rather sparse Says it needs the app.rt cookie, which we have set...but seems it needs more.

    • F

      Solved What does the new CIMD Domains feature do in FusionAuth?

      Frequently Asked Questions (FAQ)
      • cimd oauth client registration mcp • • FASupportBot
      2
      0
      Votes
      2
      Posts
      9
      Views

      F

      The CIMD Domains feature allows you to dynamically register OAuth clients using the Client ID Metadata Documents (CIMD) OAuth extension. This is not specific to MCP (Model Client Protocol), but rather is designed to support Model Context Protocol (MCP) clients—AI assistants like Claude or ChatGPT that need to connect to your MCP server.

      Note: This feature requires an Enterprise plan and is available since FusionAuth version 1.70.0.

      What It Does

      With CIMD, instead of manually registering each OAuth client in FusionAuth, the client_id itself is an HTTPS URL that points to a JSON document describing the client (its name, redirect URIs, and other metadata). When a user initiates a login flow, FusionAuth:

      Fetches the client metadata document from the URL Validates the document against configured CIMD domains Automatically registers the client just-in-time Caches the client information Proceeds with the OAuth authorization flow Why It Exists

      The Model Context Protocol creates a trust challenge: AI clients like claude.ai or chatgpt.com cannot pre-register with every MCP server in existence. CIMD solves this by allowing you to trust entire origins (like https://claude.ai) rather than individual clients, enabling dynamic registration without manual setup for each client.

      How to Configure

      You configure CIMD domains at the Tenant level. Each CIMD domain represents one trusted origin that clients may register from (e.g., https://claude.ai). You can also use a wildcard * to accept clients from any origin (though this cannot be mixed with specific domains).

      Key Constraints PKCE is required for all CIMD clients Only authorization_code and refresh_token grant types are supported User consent is always required (CIMD clients are treated as third-party clients) Redirect URIs must exactly match what's in the client's metadata document Magic links, passkeys, and IdP-initiated SAML v2 login are not supported Clients must send exactly one resource parameter matching the domain's authorized resource URIs Related Documentation CIMD Domains Concepts — comprehensive overview of CIMD domains and how to manage them OAuth Client Registration with CIMD — details on how CIMD integrates with OAuth client registration Host a Client ID Metadata Document — step-by-step guide for publishing and using CIMD documents Understanding Model Context Protocol — background on MCP and why CIMD is important for AI integrations CIMD Security Considerations — security controls and best practices for CIMD
    • F

      Solved Can user_support_manager role modify user email addresses in FusionAuth?

      Frequently Asked Questions (FAQ)
      • roles permissions user-management api security • • FASupportBot
      2
      0
      Votes
      2
      Posts
      8
      Views

      F

      The user_support_manager role is intentionally restricted from modifying identity information that could be used for authentication, including email addresses and usernames. This is a security measure to prevent potential account takeover scenarios.

      According to the FusionAuth role documentation, the user_support_manager role allows editing users except for authentication-related identity information.

      If you need to grant the ability to change user email addresses, the minimum required role is user_manager. There is no built-in role between user_support_manager and user_manager that allows email modification while restricting other permissions.

      If you need more granular control over what operations are permitted, you should implement custom logic using the FusionAuth API. This approach allows you to:

      Control exactly which fields can be modified Implement your own authorization logic Add additional security checks or approval workflows

      Using the API gives you full flexibility to define permission boundaries that match your specific security requirements.

    • F

      Solved How do I migrate from FusionAuth Cloud to self-hosted for data residency?

      Frequently Asked Questions (FAQ)
      • cloud migration self-hosted database licensing • • FASupportBot
      2
      0
      Votes
      2
      Posts
      11
      Views

      F

      To migrate from FusionAuth Cloud to self-hosted, follow this high-level process:

      Migration Steps Request a database export from FusionAuth Support Match versions: Ensure your self-hosted FusionAuth and database versions match your current Cloud deployment before migrating Load the export into your PostgreSQL instance Configure your self-hosted instance to connect to that database

      Refer to the Migrate from FusionAuth Cloud documentation for detailed steps.

      Licensing

      Your plan includes both production and non-production license keys (available at account.fusionauth.io) :

      Use the non-production key across dev and staging environments Use the production key for your production environment Keeping Your Instance Updated Most updates require no downtime Releases with database schema changes are flagged in the release notes and need a brief pause during migration Always back up your database before updating By default, FusionAuth won't apply database schema changes automatically in production. You can either: Enable silent mode for automatic migration on startup, or Run migration scripts manually before upgrading See database migrations documentation for more details Multi-node Deployment Updates

      If running multiple FusionAuth nodes, you can update using:

      Rolling updates: Update nodes one at a time (details) Blue-green deployment: Switch traffic to a fully updated set of nodes (details)

      Either approach limits downtime to the brief pause during database migration.

      Recommended Next Steps Contact FusionAuth Support to initiate the database export Confirm your current FusionAuth and database versions Set up and test dev and staging environments before migrating production Review the Cloud-hosted vs. self-hosted comparison
    • F

      Solved How can I disable MFA for a locked-out admin user in FusionAuth?

      Frequently Asked Questions (FAQ)
      • mfa two-factor api recovery-codes admin • • FASupportBot
      2
      0
      Votes
      2
      Posts
      4
      Views

      F

      If an admin user is locked out due to MFA, you have several options:

      Use Recovery Codes (if available): If the user previously generated recovery codes, they can use one of those codes to complete the MFA challenge and regain access. Once logged in, they can disable or reconfigure MFA.

      Generate Recovery Codes via API: Another admin with API access can generate recovery codes for the locked-out user using the Generate Recovery Codes API endpoint:

      POST /api/user/two-factor/recovery-code/{userId}

      Replace {userId} with the locked-out user's ID. This will generate new recovery codes that can be shared with the user to complete their MFA challenge.

      Have Another Admin Disable MFA: If you have another admin user with access to the FusionAuth admin UI, they can navigate to the locked-out user's account and disable MFA directly from the user management interface. Users with the admin role can remove MFA methods from any user without requiring a one-time verification code. Navigate to Users → Manage User → Multi-Factor tab, click the red trash can icon next to the MFA method, and confirm the removal.

      Use the User API to Remove MFA: An admin with API access can also remove MFA methods by updating the user object directly. Retrieve the user via the User API, remove the methods from the twoFactor array, and then PUT the updated user back. Note that you must use PUT (not PATCH) due to how array handling works:

      # Retrieve the user curl -XGET -H "Authorization: $API_KEY" \ 'https://your-fusionauth-url/api/user/{userId}' # Remove the twoFactor array entries and PUT the user back curl -XPUT -H 'Content-type: application/json' \ -H "Authorization: $API_KEY" \ 'https://your-fusionauth-url/api/user/{userId}' \ -d '{user object with twoFactor array cleared}'

      Important Note: The standard Disable Multi-Factor API (DELETE /api/user/two-factor/{userId}) is not suitable for this situation, as it requires a valid verification code or recovery code from the user to complete the request. This API is designed for users who can still authenticate.

      These approaches allow you to restore access without losing the security benefits of MFA for other users.

      Related Documentation Multi-Factor Authentication (MFA) - Disable MFA on a User Generate Recovery Codes API Retrieve Recovery Codes API Recovery Codes Overview Disable Multi-Factor API (requires verification code - not suitable for locked-out users) The mfa_deleter Role (for support teams with restricted permissions) User Support Guide - Remove an MFA Method
    • F

      Solved How to install a custom password hashing plugin and ensure correct package naming?

      Frequently Asked Questions (FAQ)
      • plugin password hashing installation configuration • • FASupportBot
      2
      0
      Votes
      2
      Posts
      5
      Views

      F

      Package Naming Requirement

      FusionAuth has a specific package naming requirement for plugins: the @PluginModule class must be in a package that has a parent package named "plugin" or "plugins".

      For example:

      ✅ au.com.company.fusionauth.plugins.product.MyPluginModule ✅ au.com.company.fusionauth.plugin.product.MyPluginModule ❌ au.com.company.fusionauth.product.MyPluginModule (will be skipped silently)

      If the package structure doesn't follow this convention, FusionAuth will skip the plugin JAR without displaying an error.

      Installation Process

      Create the plugins directory in your FusionAuth installation (peer to the bin and config directories):

      Linux/macOS: /usr/local/fusionauth/plugins Windows: \fusionauth\plugins

      Place the plugin JAR file in the FusionAuth plugins directory

      Restart FusionAuth (this will cause 1-2 minutes of downtime)

      Check the startup logs for confirmation messages:

      INFO io.fusionauth.api.plugin.guice.PluginModule - Installing plugin [au.com.company.fusionauth.plugins.product.MyPluginModule] INFO io.fusionauth.api.plugin.guice.PluginModule - Plugin successfully installed Confirming Plugin Installation

      You can verify that your custom password hashing plugin loaded successfully through the Admin UI:

      Navigate to Tenants → [Your Tenant] → Password Scroll to Cryptographic hash settings Look for your custom scheme(s) in the Scheme dropdown field

      If your custom schemes appear in this dropdown, the plugin has been successfully installed.

      Updating a Plugin

      When replacing a plugin version:

      Remove the old JAR file from the plugins directory (don't leave multiple versions installed if they register the same scheme names) Install the new JAR file Restart FusionAuth Verify the new version loaded via the startup logs

      Note: You should never delete an installed password hashing plugin unless you are certain that no users are using the hash provided by that plugin. If any users still have that encryptionScheme associated with their account, FusionAuth will not be able to validate their password.

      Plugin Persistence Through Upgrades

      Plugins should generally persist through FusionAuth version upgrades. However, since FusionAuth bundles its own Java runtime and that runtime version can change between major FusionAuth versions, you may need to rebuild your plugin for compatibility with newer Java versions. It's advisable to test plugin compatibility when planning FusionAuth upgrades.

      Java Compatibility Note

      FusionAuth ships with its own bundled Java runtime. The version depends on your FusionAuth version. For example, FusionAuth 1.70.0 uses Java 25. If your plugin is compiled for Java 17, it should be compatible with Java 25 (forward compatibility), but always test in your environment to confirm.

      Related Documentation Writing a Plugin - Install the Plugin - Detailed installation instructions and directory structure Writing a Plugin - Create the Guice Binding - Package naming requirements for plugins Custom Password Hashing - Overview of custom password hashing plugins Troubleshooting Custom Password Hashing Plugins - Common issues and verification steps Custom Password Hashing - Deleting Plugins - Important considerations when removing plugins Password Hashing Plugins Overview - General information about FusionAuth's plugin mechanism Example Password Encryptor Plugin - Sample plugin project on GitHub
    • F

      Solved How to allow MFA deletion for users without verified email or phone?

      Frequently Asked Questions (FAQ)
      • mfa roles api saml admin-ui • • FASupportBot
      2
      0
      Votes
      2
      Posts
      5
      Views

      F

      The mfa_deleter role has hard requirements that cannot be bypassed. To remove MFA methods using this role, the target user must be notifiable through at least one verified primary identity:

      Verified email + configured tenant.emailConfiguration.adminTwoFactorMethodRemoveEmailTemplateId, OR Verified phone number + configured tenant.phoneConfiguration.adminTwoFactorMethodRemoveTemplateId

      These requirements are by design and cannot be adjusted. The mfa_deleter role includes these safeguards to reduce the risk of abuse—when an MFA method is removed via this role, FusionAuth sends a notification to the affected user, so they must have a verified communication channel available.

      Workarounds

      You have two options to remove MFA for users without verified contact information:

      1. Use the Admin role

      Users with the Admin role are not subject to these verification requirements and can remove MFA methods from any user in the Admin UI.

      2. Use the API

      Remove MFA methods programmatically using the Update a User API:

      PATCH /api/user/{userId} Authorization: <your-api-key> Content-Type: application/json { "user": { "twoFactor": { "methods": [] } } }

      This approach allows you to build a custom support tool that removes MFA without granting full admin privileges to support staff.

      Related Documentation The mfa_deleter Role - Details on the mfa_deleter role's constraints and requirements User Support Guide: Remove an MFA Method - Step-by-step instructions for using the mfa_deleter role Update a User API - API documentation for updating user properties, including MFA methods Admin Roles - Complete list of FusionAuth Admin UI roles and their permissions Admin Two-Factor Authentication Method Removed Email Template - Template used for notifications when admin removes MFA Admin Two-Factor Authentication Method Removed SMS Template - SMS template for MFA removal notifications
    • F

      Solved When will FusionAuth support android:apk-key-hash: origins for passkey sign-in?

      Frequently Asked Questions (FAQ)
      • passkey webauthn android authentication bug • • FASupportBot
      2
      0
      Votes
      2
      Posts
      9
      Views

      F

      This issue has been fixed and released. The bug preventing FusionAuth from accepting android:apk-key-hash: origins for Android passkey authentication was addressed in a recent release.

      The fix went through the standard development and review process:

      Bug categorized and prioritized Fix implemented by the development team Code review completed Released in a subsequent version

      You can verify the fix is working in your environment by testing passkey registration and authentication flows on Android devices. The android:apk-key-hash: origin format should now be properly recognized during WebAuthn operations.

      For similar issues in the future, you can track progress on FusionAuth's GitHub issues page and monitor release notes for bug fix announcements.

    • P

      Unsolved 403 on the post-login passkey offer when re-authentication is enabled only by an application override

      Q&A
      • • • pragnesh.nonghanvadra
      2
      0
      Votes
      2
      Posts
      249
      Views

      mark.robustelliM

      @pragnesh-nonghanvadra If you can share your configuration settings and reproducible steps, i will try to go through it.

    • P

      Unsolved P2/Sev2

      Q&A
      • • • paakhi.iyer
      2
      0
      Votes
      2
      Posts
      114
      Views

      mark.robustelliM

      @paakhi-iyer

      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.

      I did find some changes that are within your version range of changes:

      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.

      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."

      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. (1.69.0 Guide)

      Suggested checks

      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.
    • S

      Unsolved Is 1.68.0 affected by the account-takeover vulnerability fixed in 1.69.2?

      Q&A
      • • • scott-m1dtya
      2
      0
      Votes
      2
      Posts
      187
      Views

      mark.robustelliM

      @scott-m1dtya 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.

    • F

      Solved How to prevent performance issues from unbounded login history growth?

      Frequently Asked Questions (FAQ)
      • performance login-records database retention configuration • • FASupportBot
      2
      0
      Votes
      2
      Posts
      5
      Views

      F

      To prevent performance degradation from unbounded login history growth, you should configure a retention period in your Login Record Settings rather than keeping unlimited history.

      Recommended Configuration Navigate to Settings → System → Advanced → Login Record Settings Enable auto-deletion of login records Set a retention period (365 days is a common best practice) Once configured, records older than your specified retention period will be removed on a rolling basis What to Expect Zero downtime: This is a simple configuration change that does not require any system downtime Initial cleanup: After setting the retention period, FusionAuth will automatically delete existing records that exceed the retention threshold. Any existing login records older than the configured number of days become eligible for deletion based on this configuration — they are not grandfathered in. Rolling maintenance: Going forward, old records are automatically cleaned up, preventing the tables from growing indefinitely Implementation Options

      You can make this configuration change yourself during a convenient time. The change can be applied through:

      Admin UI: Navigate to Settings → System → Advanced → Login Record Settings System Configuration API: Use a PATCH or PUT request to /api/system-configuration with the loginRecordConfiguration settings Terraform: Configure the login_record_configuration block in your system configuration resource

      This proactive maintenance helps ensure your FusionAuth instance remains performant as your user base and login volume grow over time.

      Related Documentation Update System Configuration API - Request Body - Details on configuring login record retention via API, including the loginRecordConfiguration.delete.enabled and numberOfDaysToRetain parameters Terraform System Configuration Resource - Configuration reference for managing login record settings with Terraform Search Login Records API - API for searching and paginating through login records Export Login Records API - API for exporting login records to CSV format
    • F

      Solved How to perform load testing on FusionAuth for spiky traffic patterns?

      Frequently Asked Questions (FAQ)
      • load-testing performance cloud rate-limiting • • FASupportBot
      2
      0
      Votes
      2
      Posts
      239
      Views

      F

      Load testing FusionAuth typically involves using a modern tool like k6 to simulate your expected traffic patterns. Here's the general approach:

      Use k6 or other HTTP-capable load testing tools: While k6 is a good modern option, FusionAuth can be load tested with any HTTP-capable load testing tool such as Gatling, JMeter, or Locust. FusionAuth also provides an open source load testing repository with pre-built scenarios including creating tenants and applications, registering users, logging users in via the Login API, and full Authorization Code grant flows.

      Profile your traffic: 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 p95 (95th percentile) response time to understand the experience of your slowest users.

      Test in a production-like environment: 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 Business Cloud or High-Availability plan 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.

      Notify FusionAuth if testing on Cloud: 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.

      Monitor the right components: Performance bottlenecks are typically the database or CPU nodes. 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.

      IP allowlisting considerations: 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.

      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.

      Related Documentation Load Test Documentation - Comprehensive guide on load testing FusionAuth, including tool recommendations and best practices FusionAuth Load Tests GitHub Repository - Open source load testing scripts with pre-built scenarios Handling Spiky Game Traffic: Registration & Autoscaling Best Practices - Specific guidance for handling spiky traffic patterns during high-demand scenarios FusionAuth Cloud High Availability Architecture - Details on HA deployment options for production-like testing FusionAuth Cloud Security - Information about Cloud security protections and rate limiting Troubleshooting Performance - Guide for troubleshooting performance issues Scaling Your Auth - Best Practices for Performance and Security - General guidance on scaling authentication systems
    • F

      Solved Can I reuse the same FusionAuth license key across dev, staging, and production?

      Frequently Asked Questions (FAQ)
      • license migration self-hosted deployment environment • • FASupportBot
      2
      0
      Votes
      2
      Posts
      230
      Views

      F

      Yes, you can use your FusionAuth licenses across multiple environments, but you should use the appropriate license type for each:

      License Structure

      In your account portal at account.fusionauth.io, you should see two licenses:

      Production License — use this for your production environment only Non-Production License — use this for your dev and staging environments Best Practice Deploy the Non-Production license to your dev and staging instances Deploy the Production license to your production instance

      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.

      Important Notes

      The non-production license can be used across as many non-production environments as you need — 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.

      Do not use the production license on non-production environments — this would cause test logins to count toward your Monthly Active Users (MAU) and affect your billing.

      License costs are not based on the number of instances — whether you have 1, 2, or 100 instances, the license cost is related only to your plan tier and MAU count.

      Using self-hosted licenses won't affect your FusionAuth Cloud deployment — the licenses operate independently, so activating your license keys on self-hosted instances will not disrupt your existing managed environment.

      Related Documentation Licensing Documentation — Overview of FusionAuth licensing concepts License FAQ: Non-Production Licenses — Details on using licenses for dev/QA/UAT servers License FAQ: Multiple Deployments — How license costs work with multiple instances Account Portal Documentation — Where to find your license keys Cloud vs Self-Hosted — Comparison of hosting options
    • F

      Solved Why is `act` claim now reserved in 1.70.0? Lambda silently fails with no warning

      Frequently Asked Questions (FAQ)
      • jwt lambda claims upgrade 1-70-0 • • FASupportBot
      2
      0
      Votes
      2
      Posts
      112
      Views

      F

      The act claim was reserved in FusionAuth 1.70.0 because it is defined in RFC 8693 (OAuth 2.0 Token Exchange) 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.

      Why This Is Classified as Minor

      FusionAuth follows semantic versioning, and this change was classified as minor rather than breaking because:

      The act claim is a standardized RFC claim 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

      However, the lack of logging when a reserved claim is silently discarded is a valid concern and makes troubleshooting difficult.

      Recommended Solutions 1. Use a Custom Claim Namespace

      Instead of using act directly, use a namespaced custom claim that won't conflict with RFC-defined claims:

      // In your JWT populate lambda jwt['https://yourapp.com/actor'] = 'your-actor-id';

      This approach is standard practice in OAuth/OIDC and prevents future collisions with reserved claims.

      2. Use applicationId or Other Non-Reserved Claims

      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).

      Why Reserved Claims Cannot Be Overridden

      Reserved claims like act, sub, iss, aud, etc., are protected because they have specific meanings defined by RFCs and must maintain consistent behavior for:

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

      If you're currently using act in production:

      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

      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.

      Related Documentation JWT Populate Lambda - Documentation on customizing JWT claims with lambdas Client Credentials JWT Populate Lambda - Documentation for lambdas in the Client Credentials grant OAuth Token Exchange (RFC 8693) - FusionAuth's implementation of RFC 8693, which defines the act claim FusionAuth 1.70.0 Release Notes - Release notes for version 1.70.0 FusionAuth 1.70 Announcement: Token Exchange - Blog post explaining the new token exchange feature and scoped delegation GitHub Issue #1721: JWT claim overriding, namespacing or the ability to unreserve claims - Open issue discussing the ability to override or unreserve claims Additional Context on Reserved Claims

      As of FusionAuth 1.70.0, the following claims are reserved in JWT Populate Lambdas and cannot be modified:

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

      Note: The exp claim can be lowered (shortened) but not extended or removed.

      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.

    • danD

      Solved different password complexity for same users in a tenant

      Q&A
      • password complexity tenants • • dan
      2
      0
      Votes
      2
      Posts
      582
      Views

      danD

      Unfortunately, lambdas won't help here. FusionAuth never exposes the password anywhere lambda code can access it, so you can't write a lambda that validates complexity.

      You do have several other options, each with tradeoffs:

      Low complexity for everyone, with MFA for franchise managers. Configure the tenant with low complexity rules and require MFA for the franchise manager group using the MFA lambda. The MFA lambda can be combined with most of the other options below.

      Low complexity for everyone, with an IdP for franchise managers. Add an identity provider pointing to a different FusionAuth instance/tenant or a corporate directory, and have franchise managers authenticate there.

      The FusionAuth instance can have more complex password requirements. Add a Login Validation lambda that denies login for users in the franchise manager group unless they authenticated through that IdP. Modify the theme to hide the IdP button on the normal login page. Pass an idp_hint on the authorization URL for everyone in the franchise manager group.

      Passwordless for restaurant staff. Let restaurant staff log in without a password and set higher complexity rules at the tenant level for everyone else.

      Two tenants with separate applications. Create tenant A (low complexity) and tenant B (high complexity). Have the restaurant staff application use tenant A's ID and the franchise manager application use tenant B's ID. You could also use a universal application to represent the application.

      Two tenants with a connector. Again, tenant A is low complexity and tenant B is high complexity.

      Set up a connector from tenant B to tenant A, with MFA lambda rules in tenant B for franchise managers. Configure the connector to not migrate users. Have all users log in to the application in tenant B, which checks tenant A for restaurant staff.

      All of these will work, but they have tradeoffs. Some may increase your MAU count, and some may add latency.

      Why not per-application password rules?

      As an aside, I don't expect FusionAuth to ever support different password rules per application, because it would lead to confusing user experiences:

      If the staff app requires 10 characters and the manager app requires 15, and a user registers in the staff app, what happens if/when they log in to the manager app? Do we deny the login? Force a password change? If the staff app requires 10 to 20 characters and the manager app requires 25 to 35, no single password can satisfy both. Would a user have to change their password every time they switch between the two apps? Can you migrate users between applications?
    • F

      Solved WebAuthn passkey registration fails on Android with origin validation error in 1.69.2

      Frequently Asked Questions (FAQ)
      • webauthn passkey android credential manager • • FASupportBot
      2
      0
      Votes
      2
      Posts
      237
      Views

      F

      This is a confirmed bug in FusionAuth 1.69.2. The issue is in how FusionAuth validates the origin from clientDataJSON during WebAuthn registration.

      This has been fixed and will be released in the next release. Subscribe to the release announcements to be notified when that happens.

    • F

      Solved Is `auth_time` in refresh token metadata reliable for MFA + PASSWORD flows?

      Frequently Asked Questions (FAQ)
      • refresh-token metadata mfa authentication api • • FASupportBot
      2
      0
      Votes
      2
      Posts
      172
      Views

      F

      The data sub-object containing auth_time and authentication_type in refresh token metadata is not currently a documented or officially supported feature in FusionAuth. Its presence is inconsistent across authentication flows, as you've observed — it appears for some authentication types but not others (notably absent for MFA + PASSWORD flows).

      According to the official documentation, the only documented fields within refresh token metaData are:

      metaData.device — An object containing device information (name, type, description, lastAccessedAddress, lastAccessedInstant) metaData.scopes — An array of OAuth scopes associated with the token metaData.resources — An array of resource URIs per RFC 8707 (available since v1.67.0)

      The data sub-object with auth_time and authentication_type that you're observing is not part of the documented API contract. Because this is undocumented behavior, you should not rely on it in production code, as it may change or be removed in future versions without notice.

      Important Distinction: auth_time on JWTs vs Refresh Tokens

      Note that auth_time is a standard and documented claim on access tokens and ID tokens (the JWTs themselves), where it represents the time of initial authentication. However, it is not a documented field on the refresh token record itself when queried via the retrieval API.

      Related Documentation Retrieve Refresh Tokens API — Official API documentation including the complete response body structure for refresh tokens Access Token and ID Token Claims — Where auth_time is officially documented as a JWT claim Multi-Factor Authentication (MFA) — Guide to implementing MFA in FusionAuth JWT Refresh API — How to use refresh tokens to obtain new access tokens