bug : Authentication throwing invalid token error

[Adarsh-jaiss]

• user Authentication throwing invalid token error, even if everthing is perfect
  

• After removing abort function from the JWT Authentication function, this is the response :

and these are server logs :

Token found in the header
NEVER PRINT SECRET eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VybmFtZSI6ImR1bW15X3VzZXIiLCJyb2xlIjoiYWRtaW4ifQ.KvN2yvobSh2PCgLbWCB9P8J9T7jV_q4gJ8P8vCzkn14
token parsed! ---------------->>>>>>>>
code fat rha hai bhai!!!!!!!!!:
{adarsh@gmail.com adarsh@123}
email found!
auth params password :adarsh@123
user password :adarsh@123
password matched!
token from auth_handler.go:  eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJlbWFpbCI6ImFkYXJzaEBnbWFpbC5jb20iLCJleHBpcmVzIjoxNzExMDQ2MzUxfQ.DPs_PQ5383fwmCIqsED1Y5yyv5MMjm3HJ4mw7DC6buw
token created!
[GIN-debug] [WARNING] Headers were already written. Wanted to override status code 401 with 200
response sent!