Most of the plugin types don't communicate with Eloqua directly since the queue worker takes care of it. We should not require the Eloqua ClientFactory be used where it is not needed.

If we allow plugins to set requiresConfiguration = TRUE, then we need to be able to respond to the configure request through the bulk API and set requiresConfiguration = FALSE.

related to #3

Currently, any query parameter that includes an encoded space (i.e. a + from Eloqua) will break the Oauth validator. There seems to be something strange about how Eloqua hashes the OAuth stuff versus how we do?

We are providing themed content to Eloqua in the menu service, and in the configure responses to other services.
We should have a theme that looks appropriate in the Eloqua interface.

Currently the plugins are executed by the controller and the results are placed on the queue(s) for transmission to Eloqua via the bulk API. It might make more sense to move the execution into the queueWorker (or add new queueWorkers?) so that they are not all executed as part of the notification/execute request from Eloqua.

The controller update method currently just returns a render array including whatever is delivered by a plugin's update method. We also need to be able to request an updated field list if there is actual configuration via an update form.