I have been attempting to setup oauth for use with my xml-rpc (through services).

1) Enable the modules.

2) visit admin/settings/oauth and add a context (follows)

$context = new stdClass;
$context->disabled = FALSE; /* Edit this to true to make a default context disabled initially */
$context->api_version = 1;
$context->name = 'imislogin';
$context->title = 'IMIS Login';
$context->authorization_options = array(
  'access_token_lifetime' => 0,
  'page_title' => 'Login to @appname',
  'message' => 'Hi @user! Click on the "login" button to log in to @appname. This will log you in to @appname and give it access to details like your username and email, but not to your password.',
  'warning' => 'Click here if you didn\\\'t ask to be logged in to @appname.',
  'deny_access_title' => 'Cancel',
  'grant_access_title' => 'Login',
  'disable_auth_level_selection' => 1,
  'signature_methods' => array(
    0 => 'HMAC-SHA1',
    1 => 'HMAC-SHA256',
    2 => 'HMAC-SHA384',
    3 => 'HMAC-SHA512',
  ),
  'default_authorization_levels' => array(
    0 => 'basic',
  ),
);
$context->authorization_levels = array(
  'basic' => array(
    'name' => 'basic',
    'title' => 'Yes, I want to log in to @appname as @user',
    'description' => 'This will log you in to @appname and give it access to details like your username and email, but not to your password.',
    'default' => 1,
    'delete' => 0,
  ),
);

3) Visit /user/1/oauth/consumers and add a consumer with name and callback = http://mysite.com/oauth/request_token

4) Visit http://term.ie/oauth/example/client.php and enter endpoint http://mysite.com/oauth/request_token as well as the consumer key & secret.

5) Press "Request Token"

This results in a WSOD. No errors logged, no output of any sort. I already verified my consumer key/secret was correct and there was no trailing or leading spaces. I saw an issue from last year similar to this #1368910: White screen for request_token/authorize/access_token pages for 7.x but it seems to have been resolved.

Comments

Version:6.x-3.0-beta4» 6.x-3.x-dev

I just updated to the development release and am still seeing this issue persist. At this point the module is unusable and I cannot secure my web services.

Further update: The patch http://drupal.org/node/1264390#comment-5860044 has resolved this issue

Status:Active» Needs review

Status:Needs review» Closed (duplicate)

There's no patch here so closing this as a duplicate per the issue queue handbook status guidelines. If the other issue has a patch that fixes your problem, mark that one as needs review.