Pipeline to extract trust info from SP metadata

[enriquepablo]

All Submissions:

• [ x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• [ x] Have you added an explanation of what problem you are trying to solve with this PR?
• [ x] Have you added information on what your changes do and why you chose this as your solution?
• [ x] Have you written new tests for your changes?
• [ x] Does your submission pass tests?
• [ x] This project follows PEP8 style guide. Have you run your code against the 'flake8' linter?

[leifj]

Need to talk about some of those points. I like the code overall.

[leifj]

Is there a reason not to add this data into the discojson structure?

[enriquepablo]

Well the discojson contains metadata for a list of IdPs, and this contains trust info for a list of SPs... The usage then in the MDQ server is different for each list - so to put both in the same structure I think we would want a pair of separated lists

[leifj]

yeah that makes sense. Maybe we should make this really clear by having a discojson for IdPs and one for SPs because we really do need to have all the SPs available to the discovery UX anyway (displayname etc)

[enriquepablo]

I'm not sure I understand - who would consume the list of SP metadata? The SA button is already in the SP login page so I wouldn't think it needs the SP md?

[leifj]

We should probably change this to some NS related to seamlessaccess. In reality we will never be able to get this stuff published through OASIS since the SSTC shutdown. I suggest we change the NS in the spec and code to https://seamlessaccess.org/NS/trustinfo

[leifj]

and also sync this with @Zacharias to make sure we talk to seamlessaccess about this

[enriquepablo]

I will do that