HTTPResource and multiple Metadata Provider files

[Jeffrey Crawford]

Greetings,

We are looking at doing something kinda similar to what Keith Wessel does
with HTTPResource and attribute filters, but using metadata providers and
metadata attribute filters instead (We found it to be more flexible)

I've gotten it working on our test rig, but I wanted to make sure what I'm
proposing on the technical side isn't possible in a better way, or someday
we say "Hey we were relying on that bug you fixed!" :)

We want to load InCommon metadata using various filters in the following
order:
metadata-providers-local-override.xml
metadata-providers-remote-uc-approved.xml
metadata-providers.xml

The first two files would need to whitelist the entities in which we want
to add additional attributes, so we don't load the entire InCommon metadata
three times. But the last one would be the fall through that loads metadata
in it's entirety. I'm finding that which ever file lists the metadata first
will have it's attributes or lack of attributes as the metadata descriptor
entry. Is this expected behavior?

Also is the HTTPResource only available in IDP30?

​​Thanks

Jeffrey E. Crawford
Enterprise Service Team <jeffreyc at ucsc.edu>

Both pilots and IT professionals require training and currency before
charging into clouds!
---------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160819/55557e54/attachment-0001.html>