<?php

[0] Fix | Delete

[1] Fix | Delete

namespace Eher\OAuth;

[2] Fix | Delete

[3] Fix | Delete

/**

[4] Fix | Delete

* The PLAINTEXT method does not provide any security protection and SHOULD only be used

[5] Fix | Delete

* over a secure channel such as HTTPS. It does not use the Signature Base String.

[6] Fix | Delete

* - Chapter 9.4 ("PLAINTEXT")

[7] Fix | Delete

*/

[8] Fix | Delete

class PlainText extends SignatureMethod {

[9] Fix | Delete

public function get_name() {

[10] Fix | Delete

return "PLAINTEXT";

[11] Fix | Delete

}

[12] Fix | Delete

[13] Fix | Delete

/**

[14] Fix | Delete

* oauth_signature is set to the concatenated encoded values of the Consumer Secret and

[15] Fix | Delete

* Token Secret, separated by a '&' character (ASCII code 38), even if either secret is

[16] Fix | Delete

* empty. The result MUST be encoded again.

[17] Fix | Delete

* - Chapter 9.4.1 ("Generating Signatures")

[18] Fix | Delete

*

[19] Fix | Delete

* Please note that the second encoding MUST NOT happen in the SignatureMethod, as

[20] Fix | Delete

* Request handles this!

[21] Fix | Delete

*/

[22] Fix | Delete

public function build_signature($request, $consumer, $token) {

[23] Fix | Delete

$key_parts = array(

[24] Fix | Delete

$consumer->secret,

[25] Fix | Delete

($token) ? $token->secret : ""

[26] Fix | Delete

);

[27] Fix | Delete

[28] Fix | Delete

$key_parts = Util::urlencode_rfc3986($key_parts);

[29] Fix | Delete

$key = implode('&', $key_parts);

[30] Fix | Delete

$request->base_string = $key;

[31] Fix | Delete

[32] Fix | Delete

return $key;

[33] Fix | Delete

}

[34] Fix | Delete

}

[35] Fix | Delete

[36] Fix | Delete