Hi, I'm trying to make a HTML5/Jquery app to use against The Movie Database API. So far so good, havn't had a single problem.
But I would like to understand the process of athenticating the user a bit better, cause I'm suspecting that I am doing it wrong to some degree.
As of now I:
However, I'm doing it this way every time. Is the token, when validated with login once, a substitute for username and password for that user forever? If so I could just store the authenticated token localy and use the preffered 2a-method the next time? The expires_at:"..." parameter makes me confused.
Yes, I'm a novice :) You were to once.
Regards, me.
Un film, une émission télévisée ou un artiste est introuvable ? Connectez-vous afin de créer une nouvelle fiche.
Vous souhaitez évaluer ou ajouter cet élément à une liste ?
Pas encore membre ?
Réponse de Bene8493
le 13 mars 2015 à 13h06
The token is just for validation. If a account has been successfully validated, you only need the
session_id
and append it to your request."The results of this query will return a
session_id
value. You should treat this value like a password. Store it securely. This is the value required in all of our write methods."Réponse de Travis Bell
le 14 mars 2015 à 10h02
There's this document that helps explain the required steps as well: https://www.themoviedb.org/documentation/api/sessions
Cheers.