You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm library some strange issues with using the library, in conjunction with the devise_token_auth.
From what I can see in Postman, the headers are being returned:
I can confirm this in the Chrome dev tools network as well:
But nothing is written to Local Storage, or the Cookies if I try that method. I added an interceptor and it seems to return undefined for the header as well.
handleLoginResponse: function(response,$auth){console.log("response");console.log(response);$auth.persistData('auth_headers',{// save the token'Authorization': 'Bearer '+response['access_token'],// convert the expiry value into a date that this module understands'expiry': newDate().getTime()+response['expires_in']});returnresponse.data;},
I get a 200 with a serialized user model (no auth_token in the serialized user model) when I sign in, just something weird happens in between!
The text was updated successfully, but these errors were encountered:
Hi Lynn,
I'm library some strange issues with using the library, in conjunction with the devise_token_auth.
From what I can see in Postman, the headers are being returned:
I can confirm this in the Chrome dev tools network as well:
But nothing is written to Local Storage, or the Cookies if I try that method. I added an interceptor and it seems to return undefined for the header as well.
I am even trying a special handleLoginResponse:
I get a 200 with a serialized user model (no auth_token in the serialized user model) when I sign in, just something weird happens in between!
The text was updated successfully, but these errors were encountered: