authentication_sp_consume_assertion:
    path:     /authentication/sp/consume-assertion
    methods:  [GET,POST] # GET is allowed on purpose to present a meaningful error message.
    defaults:
        _controller: engineblock.controller.authentication.service_provider:consumeAssertionAction

authentication_sp_process_consent:
    path:     /authentication/sp/process-consent
    methods:  [GET,POST]
    defaults:
        _controller: engineblock.controller.authentication.service_provider:processConsentAction

authentication_sp_consume_assertion:
    path:     /authentication/sp/consume-assertion
    methods:  [POST]
    defaults:
        _controller: engineblock.controller.authentication.service_provider:consumeAssertionAction

authentication_sp_process_consent:
    path:     /authentication/sp/process-consent
    methods:  [GET,POST]
    defaults:
        _controller: engineblock.controller.authentication.service_provider:processConsentAction

Allow only POST requests on /sp/consume-assertion
Allow only POST requests on /sp/consume-assertion

We stated that GET was also allowed in order to render more user
friendly error reports. That was not at all the case. In a recent effort
error reporting regarding disallowed request methods was improved.

So we can now start enforcing POST requests on the ACS endpoint. Any
other request method will result in routing exception that in turn will
be handled by the improved error reporting.

Fixes task 2 of: https://www.pivotaltracker.com/story/show/164121663
Also see: #646
