Beth Skurrie

Ron, in that scenario, the Consumer could completely miss sending the OAUTH token, and nothing in the tests would break. I understand making the request available as readonly, so that...

Are you executing pact:verify against a rack app, or are you using pact-provider-proxy to run pact:verify against an actual running server?

Sigh. It makes me sad, but I see your point Ron. @stefan-lz How are you verifying? With the normal Ruby pact:verify? Or against a running endpoint?

So, I've had a think about the nicest way we can allow people to shoot themselves in the foot. ``` ruby Pact.provider_states_for "My Jetty DropWizard App whatever that is" do...

So, @stefan-lz, if you want to make the above happen, I will reluctantly accept a pull request.

Btw, I **really** think that instead, you should create a mock authentication service. This feels dirty.

I don't know quite how drop wizard works, but do you have a rack app interface, or are you using pact-provider-proxy?

If you are using the normal `pact:verify`, then you could something like this: https://gist.github.com/bethesque/203e9d2ec08f4a40d2df No dirty hacks required! I think there's a similar thing you could do if you are...

I don't understand how you are running pact:verify if you are not using pact-provider-proxy _and_ it's not a rack app?! Can you show me the pact:verify configuration??

So you _are_ using pact-provider-proxy! See that 'require "pact/provider/proxy"' line :P Ok, I have an idea of how to do this more elegantly, but putting in another rack app between...