Project

General

Profile

Bug #180

lasso_provider_get_first_http_method does not work most of the time

Added by Benjamin Dauvergne about 11 years ago. Updated about 10 years ago.

Status:
Fermé
Priority:
Normal
Category:
Core
Target version:
Start date:
27 Jul 2010
Due date:
% Done:

90%

Estimated time:
Patch proposed:
Planning:

Description

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.

History

#1

Updated by Benjamin Dauvergne about 11 years ago

  • Target version changed from future to 2.3.1
#2

Updated by Benjamin Dauvergne about 11 years ago

  • Target version changed from 2.3.1 to 2.3.3
  • % Done changed from 0 to 90

I must verify that what I have done for endpoint storage in 2.3.1 is enough to close this bug.

#3

Updated by Benjamin Dauvergne about 10 years ago

  • Description updated (diff)
  • Status changed from Nouveau to Résolu (à déployer)

Fixed completely for SAML-2.0 with commit b7a94f2db80.

#4

Updated by Benjamin Dauvergne about 10 years ago

  • Status changed from Résolu (à déployer) to Fermé

Also available in: Atom PDF