Bug #180
Mis à jour par Benjamin Dauvergne il y a plus de 12 ans
The current implement check support for the binding on the client and on the remote provider which is useless.
We should only check for support on the remote provider. A better idea would be to check for Lasso supported bindings, and for coherence for profile having a reponse. (i.e not ARTIFACT for all profile but SingleSignOnService)
So for SingleSignOn we must check that we have a synchronous AssertionConsumer (POST, or Artifact).
For SOAP (and so all AssertionQueryRequest) no need to check support on local provider.
For Logout, NIDManagementm and NIDMapping for each synchronous binding found we check that we support another synchronous binding for the response.
We should only check for support on the remote provider. A better idea would be to check for Lasso supported bindings, and for coherence for profile having a reponse. (i.e not ARTIFACT for all profile but SingleSignOnService)
So for SingleSignOn we must check that we have a synchronous AssertionConsumer (POST, or Artifact).
For SOAP (and so all AssertionQueryRequest) no need to check support on local provider.
For Logout, NIDManagementm and NIDMapping for each synchronous binding found we check that we support another synchronous binding for the response.