@pragnesh-nonghanvadra If you can share your configuration settings and reproducible steps, i will try to go through it.
Posts made by mark.robustelli
-
RE: 403 on the post-login passkey offer when re-authentication is enabled only by an application overrideposted in Q&A
-
RE: P2/Sev2posted in Q&A
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.
-
-
RE: Is 1.68.0 affected by the account-takeover vulnerability fixed in 1.69.2?posted in Q&A
@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.
-
All Community Support Is Moving Here — Here's Why That's a Good Thingposted in Announcements
Hey everyone,
We're making a change to how we handle community support, and we wanted to share the reasoning directly with you.
We're retiring support from the #general community Slack channel and making this forum the official home for community support. Starting 10/30/2026, all community questions and peer support will live here.
Why the change?
Slack conversations disappear and be difficult to search. A great answer given to one person in a Slack channel helps only that person — and then it's gone. Forums are different. Every question asked and answered here is searchable, permanent, and available to anyone who comes after you with the same problem. That means:
When you ask a question, you're not just helping yourself. You're building a resource for the whole community.
When you answer someone else's question, your expertise lives on and continues to help people long after the conversation ends.
The collective knowledge of this community compounds over time rather than getting lost.
We believe this is genuinely better for everyone here, and we're excited to build something more lasting together.
If you have questions about the transition, feel free to post them right here.
If you are coming over from the #general Slack channel, welcome to the forum.
If you are an existing forum member, please welcome our new members by helping them out with their questions!
-
RE: FusionAuth security vulnerability: fixed by 1.69.4posted in Q&A
@damien For information on releases, please be sure to check out the release-notes. While it may not list which versions the issues were introduced in, it is recommended to stay on the latest version to avoid potential issues.
-
RE: Upgrade from 1.62.0 to 1.69.2 fails to authorize /oauth2/token requests with a 400posted in General Discussion
@chatteberg I just saw your post. If you have a paid support plan you can open a ticket. If you do not have a paid support plan, are you still experiencing the issue?
-
RE: Invalid login credentials.posted in Comments & Feedback
@anarelynevarez, Thanks for looking us up. While Buckeye Union High School District may use FusionAuth, they own the implementation of FusionAuth. You will have to reach out to them for this kind of assistance.
-
RE: Update on supporting discoverable WebAuthn credentialsposted in Q&A
@njanaskie I don't have any experience with that flow. Hopefully someone that may have had some experience with this can chime in.
-
RE: Update on supporting discoverable WebAuthn credentialsposted in Q&A
@njanaskie said in Update on supporting discoverable WebAuthn credentials:
You are right. FusionAuth does not support discoverable WebAuthn passkeys. In the page you referred to, there is some verbiage that states that directly in the credential.clientExtensionResults.credProps.rk section.
'FusionAuth does not currently support discoverable credentials (sometimes referred to as "resident keys").'
I'd recommend checking the FusionAuth GitHub issues or opening/upvoting a feature request to track progress on this.
Maybe if you tell us a little more about your use case and why the user can't enter the username/email someone can help with a work around.
-
RE: CI/CD Deployment of FusionAuth with Automatic Registrationposted in General Discussion
@nikola Have you checked out our kickstarts or APIs? You should be able to apply the license keys and configure your environments as needed.
If this isn't what you mean, please just give me a little more detail on what you are trying to do and I'll help the best I can.
-
RE: Unable to Reset Locked Account Password when MFA Enabledposted in Q&A
@anthea-mo It looks like the fix is to upgrade.
I also found this on the users accounts being locked.
If this information does not get you where you need, please let me know.
-
RE: Upgrading 1.64.1 to 1.65.0 never bootsposted in General Discussion
@mqwirtnuf How's it going? Can you share your upgrade process?
-
RE: Forgot Passwordposted in Q&A
@johnmiller I'm not 100% sure but that may be by design. You don't want to give away too much information. If it returned a specific error code, then you would know if the user exists or not.
-
RE: Send custom query param to identity provider (screen_hint)posted in Q&A
@elliotdickison Can you let us know what third party OIDC IdP you are working with?
-
Shipped: Q1 2026posted in Announcements
It's one thing to read about new features in the release notes and another to see them demo'd. If you're interested in what FusionAuth has been up to, come check it out tomorrow in our Q1 2026 edition of Shipped!
-
RE: Minimum Role Needed to Edit Specific Tenant Settingsposted in General Discussion
@batmysta I know this is a bit of a "trick" answer, but the reality is the right answer depends on what exactly you want the user to have access for. I understand that the roles in FusionAuth may give more access than you may like (I.E. MFA is a tenant level settings, but there is no role just for MFA edit.), but there are some other options.
Again, depending on what you want to do and what version you are running, there is the idea of the Tenant Manager applicaiton. This will still not help you with MFA settings thought.
The other option is using the APIs. Since everything in The FusionAuth admin UI is API first, you could create your own application that would allow users you choose to edit them.
Hope this is useful.
-
RE: The request origin could not be verified. Unable to complete this login request with same-instance cross-tenant IdP federationposted in Q&A
@hvfa Apologies for being a bit AWOL. I hope for things to slow down and be able to take a look at this a little more closely next week.
-
RE: The request origin could not be verified. Unable to complete this login request with same-instance cross-tenant IdP federationposted in Q&A
@hvfa At first glance this looks like a domain issue. Can you share an example of how your Authorized redirect URLs and Authorized request origin URLs are set up in relation to the applications. Please feel free to use example domains like https://domain1/ or https://domain2 and so on. It may also be useful to give the other OAuth settings for the applications as well (be sure to redact or obscure and sensitive information).
-
RE: Struggling to backup selfhosted fusionAuth.posted in Q&A
@ralph Thanks for following up and sharing!
