validateOptions(options) {
    if (!options) {
      throw new Error('Twitter auth options are required.');
    }

    this.enableInsecureAuth = options.enableInsecureAuth;

    if (!this.enableInsecureAuth && (!options.consumer_key || !options.consumer_secret)) {
      throw new Error('Consumer key and secret are required for secure Twitter auth.');
    }
  }
Parse Server authentication adapter for Twitter.

@class TwitterAdapter
@param {Object} options - The adapter configuration options.
@param {string} options.consumerKey - The Twitter App Consumer Key. Required for secure authentication.
@param {string} options.consumerSecret - The Twitter App Consumer Secret. Required for secure authentication.
@param {boolean} [options.enableInsecureAuth=false] - **[DEPRECATED]** Enable insecure authentication (not recommended).

@description
## Parse Server Configuration
To configure Parse Server for Twitter authentication, use the following structure:
### Secure Configuration
```json
{
  "auth": {
    "twitter": {
      "consumerKey": "your-consumer-key",
      "consumerSecret": "your-consumer-secret"
    }
  }
}
```
### Insecure Configuration (Not Recommended)
```json
{
  "auth": {
    "twitter": {
      "enableInsecureAuth": true
    }
  }
}
```

The adapter requires the following `authData` fields:
- **Secure Authentication**: `oauth_token`, `oauth_verifier`.
- **Insecure Authentication (Not Recommended)**: `id`, `oauth_token`, `oauth_token_secret`.

## Auth Payloads
### Secure Authentication Payload
```json
{
  "twitter": {
    "oauth_token": "1234567890-abc123def456",
    "oauth_verifier": "abc123def456"
  }
}
```

### Insecure Authentication Payload (Not Recommended)
```json
{
  "twitter": {
    "id": "1234567890",
    "oauth_token": "1234567890-abc123def456",
    "oauth_token_secret": "1234567890-abc123def456"
  }
}
```

## Notes
- **Deprecation Notice**: `enableInsecureAuth` and insecure fields (`id`, `oauth_token_secret`) are **deprecated** and may be removed in future versions. Use secure authentication with `consumerKey` and `consumerSecret`.
- Secure authentication exchanges the `oauth_token` and `oauth_verifier` provided by the client for an access token using Twitter's OAuth API.

@see {@link https://developer.twitter.com/en/docs/authentication/oauth-1-0a Twitter OAuth Documentation}