Latest: buggy behaviour of parent:: in PHP 5.3.3

Content with Style

Web Technique

Linkedin and Zend_Oauth

by Pascal Opitz on May 5 2010, 17:43

Matthias has made look into Linkedin and OAuth for a bit. This example was a very interesting read, but I think it's overcomplicating things slightly. That's why I want to show a very simple example inspired by what we've done for the brand new CwS Author pages.

Before we get started, some good news: No more bugs in Zend_Oauth. Hence all that hacking of the ZF code is now obsolete as well.

Also the example contained a couple of silly things that just confused me: The use of $_SESSION for example, or the fact that with ZF 1.10 the parameter was called 'userAuthorizationUrl' rather than 'userAuthorisationUrl'.

My simple example

I am assuming that we're using a controller for the user, and here's an action called linkedin for it:

public function linkedinAction() {
  $user_id = $this->loginHelper->userId();
  $ns = new Zend_Session_Namespace('linkedin_oauth');

  $options = array(
    'localUrl' => 'http://site/user/linkedin/',
    'callbackUrl' => 'http://site/user/linkedin/',
    'requestTokenUrl' => '',
    'userAuthorizationUrl' => '',
    'accessTokenUrl' => '',
    'consumerKey' => $this->config->linkedin->key,
    'consumerSecret' => $this->config->linkedin->secret,

  $consumer = new Zend_Oauth_Consumer($options);

  if(empty($ns->request_token)) {
    // get request token and redirect to linkedin
    $token = $consumer->getRequestToken();
    $ns->request_token = serialize($token);
  } else {
    try {
      // get access token and store in DB
      $token = $consumer->getAccessToken($_GET, unserialize($ns->request_token));
      $this->userModel->setLinkedinToken($author_id, serialize($token));
    } catch(Exception $e) {
      // reset token in DB and empty session if there was a fault
      $this->userModel->setLinkedinToken($author_id, '');
      $ns->request_token = '';

  // redirect user to own details page
  return $this->_redirect('/user/details/');

As you can see you'll need the infrastructure to obtain the user id and store the token in the DB, but otherwise this is pretty straight forward. We're saving the request_token in a session to then obtain the access_token when linkedin redirects us to the same page.

Assuming that you then have managed to read the token from the database, this is what you need to get the users current status:

$options = array(
  'consumerKey' => $this->config->linkedin->key,
  'consumerSecret' => $this->config->linkedin->secret,

$token = unserialize($token);
$client = $token->getHttpClient($options);

$response = $client->request();
$content = $response->getBody();

And that's it really. For more details read the great original articles here and here.


  • Great post (added a bookmark on delicious), with OAuth gaining more popularity it's great to see clean implementation to build from. Thanks

    by Chris on May 14 2010, 11:56 - #

Leave your comment

Comments are moderated.
Tags allowed: a, strong, em, code, ul, ol, li, q, blockquote, br, p