Removed warden logic because it caused a change in the headers to not have any effect.
In my example, I am using a Grape endpoint that needs to be available in a "light" version if the user is not logged in and will return more information if the user is logged in.
Thus, I played around with the request headers and noticed that the user is constantly logged in after the first log in, no matter if I changed the request headers or not. Is this the intended behaviour by devise_token_auth, as the "native" devise_token_auth endpoints behave differently?
I therefore removed the warden logic from this gem to authenticate each request by its header parameters individually.
Removed warden logic because it caused a change in the headers to not have any effect.
In my example, I am using a Grape endpoint that needs to be available in a "light" version if the user is not logged in and will return more information if the user is logged in.
Thus, I played around with the request headers and noticed that the user is constantly logged in after the first log in, no matter if I changed the request headers or not. Is this the intended behaviour by devise_token_auth, as the "native" devise_token_auth endpoints behave differently?
I therefore removed the warden logic from this gem to authenticate each request by its header parameters individually.
The according issue is #7