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