ILIAS
release_5-4 Revision v5.4.26-12-gabc799a52e6
|
The PLAINTEXT method does not provide any security protection and SHOULD only be used over a secure channel such as HTTPS. More...
Public Member Functions | |
get_name () | |
build_signature ($request, $consumer, $token) | |
oauth_signature is set to the concatenated encoded values of the Consumer Secret and Token Secret, separated by a '&' character (ASCII code 38), even if either secret is empty. More... | |
Public Member Functions inherited from OAuthSignatureMethod | |
get_name () | |
Needs to return the name of the Signature Method (ie HMAC-SHA1) More... | |
build_signature ($request, $consumer, $token) | |
Build up the signature NOTE: The output of this function MUST NOT be urlencoded. More... | |
check_signature ($request, $consumer, $token, $signature) | |
Verifies that a given signature is correct. More... | |
The PLAINTEXT method does not provide any security protection and SHOULD only be used over a secure channel such as HTTPS.
It does not use the Signature Base String.
OAuthSignatureMethod_PLAINTEXT::build_signature | ( | $request, | |
$consumer, | |||
$token | |||
) |
oauth_signature is set to the concatenated encoded values of the Consumer Secret and Token Secret, separated by a '&' character (ASCII code 38), even if either secret is empty.
The result MUST be encoded again.
Please note that the second encoding MUST NOT happen in the SignatureMethod, as OAuthRequest handles this!
Definition at line 184 of file OAuth.php.
References $key, $request, PHPMailer\PHPMailer\$token, and OAuthUtil\urlencode_rfc3986().
OAuthSignatureMethod_PLAINTEXT::get_name | ( | ) |