Setup issue #43
-
|
This is the error i am trying to solve from many hours: The JwtAuthenticationFilter runs for every request and attempts to parse the Authorization header if present. If Postman or the browser sends any header (or even an email with @), the filter throws a Base64 decoding error, blocking the login request. Root cause: Impact: |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
@ManjuVasanth Can you help him, please? |
Beta Was this translation helpful? Give feedback.
-
|
The /api/users/register and /api/users/login endpoints are public URL's and do not require a Bearer token, while all other endpoints, except /logout, require a token to access. The public URLs are functioning correctly as expected. Illegal base64 character: '@' Correct workflow will be: Then use the same email and password with: Pass this JWT token as a Bearer Token in the Authorization header for all other API requests. |
Beta Was this translation helpful? Give feedback.
The /api/users/register and /api/users/login endpoints are public URL's and do not require a Bearer token, while all other endpoints, except /logout, require a token to access. The public URLs are functioning correctly as expected.
Illegal base64 character: '@'
it means a request was sent without a valid Bearer Token, and the JwtAuthenticationFilter attempted to decode an invalid Authorization header. This happens even for public endpoints since the filter runs globally. Always ensure you pass a proper Authorization: Bearer <JWT_TOKEN> header for protected endpoints.
Correct workflow will be:
Use Postman (or any API client) to hit:
POST http://localhost:8180/api/users/register
with the re…