Currently, config server supports two types of oauth requests for PUTs and POSTs

1)  Requests with the oauth signature that includes the entire POST body (including oauth headers)

2)  Requests with the oauth signature that only includes the oauth headers

Originally, this was included to support both the Conductor method of generating oauth PUTs (option#2 above) as well as the test automation suite (option#1 above).

Eventually, we decided that it was categorically wrong to allow option#2 type requests.  The fix for this (on the conductor side) was to replace the ruby RestClient library with the Oauth library (https://bugzilla.redhat.com/show_bug.cgi?id=760592).

However, the fact that config server allowed for option#2 oauth requests hid the fact that conductor generated oauth one way and the test automation generated requests another way.

This bug is to remove the ability for configserver to handle option#2 oauth requests.  This will effectively break the conductor -> config server communication until the fix for bug #760592 is applied and moved to ON_QA.

This bug is counterintuitive in that the fix actually breaks something.  At least until bug #760592 is resolved.

How to reproduce:

1) start with a aeolus-conductor-0.9.0 (or earlier)
2) setup a config server: aeolus-configserver-0.4.5-2 (or earlier)
3) add config server to conductor under provider accounts
4) Launch a simple deployment using that config server

Actual results:

The launch should succeed.

Expected results:

The launch fails and reports a 401 (either in the conductor UI, or in the config server logs) when conductor attempts to POST the configs to config server.