Class: OAuthSignatureMethod_RSA_SHA1

Source Location: /qp_plugins/twitter_plugin/twitteroauth/oAuth.php

Class OAuthSignatureMethod_RSA_SHA1

Class Overview

The RSA-SHA1 signature method uses the RSASSA-PKCS1-v1_5 signature algorithm as defined in

[RFC3447] section 8.2 (more simply known as PKCS#1), using SHA-1 as the hash function for EMSA-PKCS1-v1_5. It is assumed that the Consumer has provided its RSA public key in a verified way to the Service Provider, in a manner which is beyond the scope of this specification.

Chapter 9.3 ("RSA-SHA1")

Located in /qp_plugins/twitter_plugin/twitteroauth/oAuth.php [line 247]

OAuthSignatureMethod
   |
   --OAuthSignatureMethod_RSA_SHA1

Author(s):

API Tags:

Abstract:

Methods

[ Top ]

Inherited Properties, Constants, and Methods

Inherited Properties

Inherited Methods

Inherited Constants

Inherited From OAuthSignatureMethod

OAuthSignatureMethod::build_signature()

Build up the signature NOTE: The output of this function MUST NOT be urlencoded.

OAuthSignatureMethod::check_signature()

Verifies that a given signature is correct

OAuthSignatureMethod::get_name()

Needs to return the name of the Signature Method (ie HMAC-SHA1)

[ Top ]

Method Summary

void	build_signature()	dummy docblock makes error-free autodocs
void	check_signature()	dummy docblock makes error-free autodocs
void	fetch_private_cert()	dummy docblock makes error-free autodocs Up to the SP to implement this lookup of keys. Possible ideas are: (1) do a lookup in a table of trusted certs keyed off of consumer
void	fetch_public_cert()	dummy docblock makes error-free autodocs
void	get_name()	dummy docblock makes error-free autodocs

[ Top ]

Methods

build_signature [line 284]

void build_signature(

$request, 
$consumer, 
$token 
)

dummy docblock makes error-free autodocs

Parameters:

	$request:
	$consumer:
	$token:

API Tags:

Access:

public

Redefinition of:

OAuthSignatureMethod::build_signature(): Build up the signature NOTE: The output of this function MUST NOT be urlencoded.

[ Top ]

check_signature [line 308]

void check_signature(

$request, 
$consumer, 
$token, 
$signature 
)

dummy docblock makes error-free autodocs

Parameters:

	$request:
	$consumer:
	$token:
	$signature:

API Tags:

Access:

public

Redefinition of:

OAuthSignatureMethod::check_signature(): Verifies that a given signature is correct

[ Top ]

fetch_private_cert [line 278]

void fetch_private_cert(

&$request 
)

dummy docblock makes error-free autodocs Up to the SP to implement this lookup of keys. Possible ideas are: (1) do a lookup in a table of trusted certs keyed off of consumer

Either way should return a string representation of the certificate

Parameters:

&$request:

API Tags:

Abstract:
Access:	protected

[ Top ]

fetch_public_cert [line 268]

void fetch_public_cert(

&$request 
)

dummy docblock makes error-free autodocs

Up to the SP to implement this lookup of keys. Possible ideas are: (1) do a lookup in a table of trusted certs keyed off of consumer (2) fetch via http using a url provided by the requester (3) some sort of specific discovery code based on request

Either way should return a string representation of the certificate

Parameters:

&$request:

API Tags:

Abstract:
Access:	protected

[ Top ]

get_name [line 253]

void get_name(
)

dummy docblock makes error-free autodocs

API Tags:

Access:

public

Redefinition of:

OAuthSignatureMethod::get_name(): Needs to return the name of the Signature Method (ie HMAC-SHA1)

[ Top ]

hic sunt dracones

	plugins Twitter

[ class tree: plugins ] [ index: plugins ] [ all elements ]