Project

General

Profile

Development #31

Use new class for metadata in LassoProvider and LassoServer implementations

Added by Benjamin Dauvergne about 9 years ago. Updated almost 4 years ago.

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

0%

Estimated time:
35.00 h
Patch proposed:
Planning:
No

Description

Current parsing for the endpoints do not keep their implicit ordering from the XML file as they are dumped into an hash-table (which is a unordered container).

Using LassoNodes objects will keep this ordering so that we can apply the order of endpoints declaration for binding preferences. A new api on LassoProvider called lasso_provider_prefered_bindings_for_profile should also be added.


Related issues

Related to Lasso - Development #30: Add node objects for the SAMLv2 metadata schema Nouveau 20 May 2010

History

#1 Updated by Benjamin Dauvergne about 9 years ago

  • Assignee set to Benjamin Dauvergne

#2 Updated by Benjamin Dauvergne almost 9 years ago

  • Category set to Core

#3 Updated by Benjamin Dauvergne about 7 years ago

  • Assignee deleted (Benjamin Dauvergne)

#4 Updated by Benjamin Dauvergne almost 4 years ago

  • Status changed from Nouveau to Fermé
  • Description updated (diff)

Fixed by storing endpoints as part of an ordered array of structures.

Also available in: Atom PDF