vijay sahu
Reputation: 823
C# IDX14100: JWT is not well formed, there are no dots (.)
Issue: after upgrading from .NET 7 to .NET 9, my application invalidates JWT tokens, leading to authentication failures. Now, I am unable to log in, as the API consistently returns HTTP "401 - Unauthorized" errors.
Symptoms:
- The JWT token is always rejected as invalid
- The issue started only after upgrading to .NET 9
- It was working perfectly in .NET 7
Question: has anyone encountered a similar issue after upgrading to .NET 9? What changes might be affecting JWT authentication?
Error message as response from JWT authentication:
IDX14100: JWT is not well formed, there are no dots (.).
The token needs to be in JWS or JWE Compact Serialization Format.
(JWS): 'EncodedHeader.EndcodedPayload.EncodedSignature'.
(JWE): 'EncodedProtectedHeader.EncodedEncryptedKey.EncodedInitializationVector.EncodedCiphertext.EncodedAuthenticationTag'.
Upvotes: 0
Views: 45
Answers (0)
Related Questions
- Problem making JWT token be interpreted in Onion architecture
- Token handler unable to convert the token to jwt token
- JWT Token authentication, expired tokens still working, .net core Web Api
- If you can decode JWT, how are they secure?
- SqlException from Entity Framework - New transaction is not allowed because there are other threads running in the session
- Issue with Using JWT for Authentication in ASP.NET Core MVC
- Error on validating JWT token IDX12741. JWT: must have three segments (JWS) or five segments (JWE)
- What are the main differences between JWT and OAuth authentication?
- How to Validate JWT token generated from one app in another?
- Unable to read JWT token generated using System.IdentityModel.Tokens.Jwt