Improve authentication API
Reported by Michael Roterman | February 24th, 2014 @ 05:11 PM | in Magnolia (closed)
Currently in my opinion the following features are missing:
- return_to_url type of parameter when validating a request token for a better flow
- account/password login support ( I believe I've seen this being added? )
Comments and changes to this ticket
-
Michael Roterman February 24th, 2014 @ 05:16 PM
Something that is missing currently is the fact I saw "Movie List" being added as the application, while the documentation as far as I've seen doesn't specify any method to announce this?
-
Travis Bell February 24th, 2014 @ 05:25 PM
return_to_url type of parameter when validating a request token for a better flow
When you make a request to the Authentication-Callback, add a ?redirect_to= param. This has always been available and used to be present in the documentation but was removed at some point. I'm not actually sure why/when. I'll make sure it's updated.
http://www.themoviedb.org/authenticate/REQUEST_TOKEN?redirect_to=www.mydomain.com
When you complete the workflow, a
?approved=true
or?denied=true
param will be appended so you can tell the status of the request.account/password login support ( I believe I've seen this being added? )
It is added, but not currently documented. Kind of a quiet feature at the moment:
https://www.themoviedb.org/authenticate/REQUEST_TOKEN/validate_with_login?username=&password=
Something that is missing currently is the fact I saw "Movie List" being added as the application
I'm not sure I understand what you're referring to. Could you elaborate?
-
Michael Roterman February 24th, 2014 @ 05:55 PM
For what I meant with the last comment, see the attached image
-
Michael Roterman February 24th, 2014 @ 05:56 PM
Thanks for the rest of your response, that clarifies :-)
-
Travis Bell February 24th, 2014 @ 05:59 PM
Ah, that should map to whatever you have entered in your account prefs, under the API details.
-
Michael Roterman February 24th, 2014 @ 06:06 PM
Ah, I expected to be able to announce the name from the actual "consumer" itself, thanks for clearing that up.
-
Michael Roterman March 3rd, 2014 @ 03:26 PM
Hi Travis,
I've just tried implementing the username and password authentication but I miss be missing something, the following request returns into a 404:
GET /3/authenticate/VALID_REQUEST_TOKEN/validate_with_login?username=VALID_USERNAME&password=VALID_PASSWORD&api_key=VALID_API_KEY
Any idea? Is this still private or...?
-
Michael Roterman March 3rd, 2014 @ 04:03 PM
See the current pull request at https://github.com/wtfzdotnet/php-tmdb-api/commit/cc0ec44b2806a43ed...
-
Travis Bell March 26th, 2014 @ 10:50 AM
- State changed from new to resolved
I'm closing this ticket as I've created a separate ticket specifically for logging into the API with a username and password here: http://tmdb.lighthouseapp.com/projects/83077/tickets/363-create-aut...
-
Travis Bell March 26th, 2014 @ 10:50 AM
- Milestone changed from Icebox to Magnolia
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »