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. - Chapter 9.4 ("PLAINTEXT")

### Methods

## 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.

    build_signature(\OAuthRequest $request, \OAuthConsumer $consumer, \OAuthToken $token) : string

The result MUST be encoded again. - Chapter 9.4.1 ("Generating Signatures")

Please note that the second encoding MUST NOT happen in the SignatureMethod, as OAuthRequest handles this!

### Parameters

#### $request

`\OAuthRequest`

#### $consumer

`\OAuthConsumer`

#### $token

`\OAuthToken`

### Returns

`string`

## Verifies that a given signature is correct

    check_signature(\OAuthRequest $request, \OAuthConsumer $consumer, \OAuthToken $token, string $signature) : bool

Inherited

inherited_from | \OAuthSignatureMethod::check_signature()

### Parameters

#### $request

`\OAuthRequest`

#### $consumer

`\OAuthConsumer`

#### $token

`\OAuthToken`

#### $signature

`string`

### Returns

`bool`

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

    get_name() : string

### Returns

`string`