search

IdentityPython / pyFF

SAML metadata aggregator
https://pyff.io/
Other
50 stars 36 forks source link

Unexpected load select, html interface behaviour #104

Closed mrvanes closed 3 years ago

mrvanes commented 7 years ago

There seems to be a discrepancy between the selected metadata for html and xml/json requests in MDServer mode. Our html interface allways shows all entities in the original metadata set, independant of any load - select pipeline whereas the xml/json 'when requests' seem to select from the filtered metadata set.

Am I right? If so, why wouldn't the html interface adhere to the preselected subset, it seems to evade the 'when request' pipeline? Worst case scenario, this results in ugly errors caused by empty xml documents because the resulting filtered set does not contain the entity shown in the html interface?

If nothing else, this could be regarded a feature request, for the html interface to respect the initialising select in the load pipeline, or a discussion about the purpose of the html interface...

pyFF version: master (1d032fe)

leifj commented 3 years ago

I'm going to close this issue since it is referring to code that is about to be deprecated and removed from pyFF. Work on the UX has moved to mdq-browser and theidentityselector/thiss-js for the admin ui and discovery service respectively.