Adds option to use a Shibboleth SP discovery feed for metadata filtering #53
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
First of all: Great work on this tool and thanks for all the work you put into it!
And now: I did exactly what I was told not to do, cloned the repository and hosted my own DiscoJuice instance :) (at least in parts)
With this pull-request I added support to filter the great number of IdPs coming from one or more of the involved federations down to ones that are actually granted access to a certain Shibboleth SP.
As far as I understand it, the Shibboleth SP provides a special discovery feed URL that gives you a list of all IdPs that are known to the SP.
With this list I filtered the federation metadata, giving me a nice small list of IdPs that are allowed to use my SP.
Example is up and running at https://fauboxtest.rrze.uni-erlangen.de
Click on "SSO Anmeldung" to see the DiscoJuice overlay with the filtered list of IdPs.
See https://fauboxtest.rrze.uni-erlangen.de/Shibboleth.sso/DiscoFeed for the generated Shibboleth SP discovery feed.
I hope this is helpful to you.
Thx and cu