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
{{ message }}
This repository was archived by the owner on Mar 22, 2022. It is now read-only.
Using the Feathers client you have to call app.authenticate() with no parameters as documented. No manual cookie setting or messing with session ids necessary.
@daffl I have the same problem, I'm using Vue js and as an end point /authentication but I can not read the Set-Cookie: feathers-jwt. Some suggestion is the same inconvenience I can see the token in the inspector but I can not read it.
# for freeto subscribe to this conversation on GitHub.
Already have an account?
#.
Steps to reproduce
on the server:
"cookie": { "enabled": true, "name": "feathers-jwt", "httpOnly": false, "secure": false, "domain": "localhost" }
app.use(cors({ origin: "http://localhost:8080", credentials: true }));
on the client I use axios:
Vue.axios.defaults.withCredentials = true
I make post to /authentication and receive setCookie on the response.
Set-Cookie:feathers-jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6ImFjY2VzcyJ9.eyJ1c2VySWQiOiI1YjExNGI...
After this I make POST request to a service. In this POST I see cookie:
connect.sid=s%3AC0M6oqh_TXRPffVDWDtGlCIFRugiSazV.9oo...
and receive 401 error. In the server I see:
error: NotAuthenticated: No auth token
Expected behavior
I think, I must receive code 200 in response
Actual behavior
I receive 401 no token
Module versions (especially the part that's not working):
NodeJS version:
9.3.0
Operating System:
ubuntu 14.04
Browser Version:
opera, chromium
The text was updated successfully, but these errors were encountered: