Details
-
Story
-
Resolution: Done
-
Minor
-
None
-
None
-
None
-
2022 Sprint 4, 2022 Sprint 5, 2022 Sprint 6, 2022 Sprint 7
Description
IdP v4.0.1 already allows for Metadata Filters to be written into a separate config file, rather than needing to be embedded into the Metadata Provider to which they apply (which is in a metadata-providers.xml file. Instead of a user needing to define, for example, the InCommon aggregate or MDQ provider first, and then add filters to it, this opens up the possibility of just starting with adding filters. But you still need to identity the Metadata Provider to which the filters should apply, so you would first need a way to configure the ShibUI with one or more "Metadata Provider IDs" that the filters should be associated with.
Info at: ByReferenceFilter
Most deployers of the Shibboleth IdP that are going to use InCommon metadata would generally already have that defined in their core IdP's metadata-providers.xml file, and not need to have it defined a "2nd time" in the ShibUI. So this allows that.
See comment below by Steve Erickson 6-22-22 for requirements change.
Attachments
1.
|
Backend |
|
Done | Charles Hasegawa (unicon.net) |
|
|||||||||
2.
|
Front End |
|
Done | Ryan Mathis (unicon.net) |
|
|||||||||
3.
|
QA & Set |
|
Done | Bill Smith (unicon.net) |
|
