Open Arti3DPlayer opened 6 years ago
What I notice that you store the token in database, but how about the session? the token generator generate responding token with the user object "admin", but each request owns an unique sessionid, so I think the token stored into the database is session-related, that is, these lead to that error above.
I hope this is the reason, or anyone else knows the fact?
token stored into the database is session-related
What does that mean ? That I can only use this token in session with which I created it ?
I created a token via admin interface.
Then do:
curl "http://0.0.0.0:8000/projects/" -H "Authorization: JWT 37fd60be49932a418aba5f9f12d39891b78acf0b"
And receive error: