Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Improve authentication API

#358

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? )

Reported by Michael Roterman · February 24th, 2014 @ 05:11 PM

State: resolved
Milestone: Magnolia
Assigned to: Travis Bell Travis Bell

Activity

  1. Michael Roterman
    Michael Roterman

    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?

    February 24th, 2014 @ 05:16 PM

  2. Travis Bell
    Travis Bell

    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?

    February 24th, 2014 @ 05:25 PM

  3. Michael Roterman
    Michael Roterman

    For what I meant with the last comment, see the attached image

    February 24th, 2014 @ 05:55 PM

  4. Michael Roterman
    Michael Roterman

    Thanks for the rest of your response, that clarifies :-)

    February 24th, 2014 @ 05:56 PM

  5. Travis Bell
    Travis Bell

    Ah, that should map to whatever you have entered in your account prefs, under the API details.

    February 24th, 2014 @ 05:59 PM

  6. Michael Roterman
    Michael Roterman

    Ah, I expected to be able to announce the name from the actual "consumer" itself, thanks for clearing that up.

    February 24th, 2014 @ 06:06 PM

  7. Michael Roterman
    Michael Roterman

    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...?

    March 3rd, 2014 @ 03:26 PM

  8. Michael Roterman
  9. Travis Bell
    Travis Bell
    • 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: #363 Create auth workflow to login via the API with a username and password

    March 26th, 2014 @ 10:50 AM

  10. Travis Bell
    Travis Bell
    • Milestone changed from Icebox to Magnolia

    March 26th, 2014 @ 10:50 AM

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.