Continuing the oauth series but before we begin, read the overview / disclaimer. On to Yahoo!…
For this tutorial you will need Oauth2 installed.
First off, ensure that you have registered your application with Yahoo! and have created the following in your settings file:
1) Create the redirect URL
Yahoo is a little bit more complicated than the previous providers in that the first step requires you to get a request token before redirecting to Yahoo!. Much like the other examples, this also requires a redirect URL and the consumer key, but we also have some new data that’s required including a timestamp, nonce (any unique string), version and language.
Once you’ve got the request token, you can use it to create the authorization URL.
2) Redirect to provider’s site
This url can now be used to redirect to Yahoo! (i.e.
3) Handle the response (approved or denied)
Once the user makes their choice to approve or deny, Yahoo! will redirect back to your redirect_url. You will need to verify the user approved the application:
If any of the above tests fail, we can safely assume the user either arrived at this page directly (i.e. by typing in the URL) or they denied the application. Either way we don’t want to proceed and should redirect them to the start of the registration flow (i.e.
4 & 5) Get an access token and the user’s profile
At this point the user has authorized your application but you don’t have actual access to their data yet. To get that you’ll need to request an access token. Notice that we’re saving the access token to the user’s session as we don’t want to request it more than once during the registration flow.
Once you have the access token, you can then make the request for the user’s profile data:
That’s it! You can now use the user’s profile information to pre-fill a registration form, perhaps skipping over fields where you already have a required value such as an email address or first and last name. Just be sure to save their Yahoo! ID along with their profile so you can use it validate them in the future. You should also save the access_token and expires values so that you can make future requests to the API for this user or refresh the access token when it has expired.
In a future post I’ll be looking at how to detect an already registered user as well as provide a login with this provider button.