Hi @jack thanks for filing the issue.
We have a bug triage process internally and I'll make sure it gets in there, reviewed and prioritized.
Users who have rights to post in the FAQ category.
Hi @jack thanks for filing the issue.
We have a bug triage process internally and I'll make sure it gets in there, reviewed and prioritized.
@pragnesh-nonghanvadra If you can share your configuration settings and reproducible steps, i will try to go through it.
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
@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.
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.
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.
All of these will work, but they have tradeoffs. Some may increase your MAU count, and some may add latency.
As an aside, I don't expect FusionAuth to ever support different password rules per application, because it would lead to confusing user experiences:
Can I enforce different password complexity rules for different groups of users (e.g., restaurant staff vs. franchise managers) logging into the same application and in the same tenant? Can a lambda help with this?
We have two kinds of users. Restaurant staff need a low-friction login with simple password rules, since they’re often signing in on shared devices or between shifts. Franchise managers can access sensitive data like payroll and financial reports, so they need stricter complexity requirements. Can we do this in a single FusionAuth setup, perhaps with a lambda?
Using FusionAuth 1.70.
Hi @david-kircheis,
The cross-platform authenticator passkey functionality is not available for the licensed community edition, only the platform passkey functionality.
The options I see for your use case are:
While we'd love to have FusionAuth used by everyone, we can't offer all features to every plan level. We recognize this limit means FusionAuth isn't the right solution for every authentication problem.
I appreciate you using FusionAuth now and hope it remains helpful to you.
@andrzej-taramina Usually, when we see 403s on the hosted backend, the root cause ends up being an origin issue.
The endpoint calls need to originate from the same domain the FusionAuth instance lives at
There's some CORS information in this section of the hosted backend docs: https://fusionauth.io/docs/apis/hosted-backend#prerequisites
In reading through this post, one of the first things that jumps to mind for me is that between those versions of FA, DPoP was introduced into both FusionAuth and the SDKs.
When first using DPoP in the SDKs (I did it in React), I ran into 401s for /app/me due to not running the requests with the additional DPoP headers.
Depending on your use case, it might make sense to switch from /app/me to using the userInfo property that comes from the SDK.
import { useFusionAuth } from "@fusionauth/vue-sdk";
const {
userInfo,
} = useFusionAuth();
userInfo has most (maybe all) of what's available on /app/me and is also a more efficient fetch for it.
Hey @sameer-syedmanzur!
If you're on any paid plan, I'd recommend looking at our Generic Messengers.
When the generic messenger is hit, it fires off a request to any HTTP endpoint you want. You can then use any method you need to to get the code to the user or post it back to the API to complete the 2nd factor.
If you're on the Community edition (free version), that's not accessible to you, though.
For solution on the community edition, check out this doc if you haven't read it yet: https://fusionauth.io/docs/lifecycle/authenticate-users/multi-factor-authentication#build-your-own-interface
That's how you set up a custom interface for TOTP. That would be the best-practice way of doing 2fa without smtp on community edition. I haven't done anything TOTP-based for testing, but I'd wager there's a TOTP application with an API that could handle this.
Depending on the use case, it might also make sense to set up something simple with something like MailTrap to do testing via SMTP instead of going through all this. That may be a problem depending on the use case, though