Artifact metadata resolution in java OpenSAML and FU question on using the MDQ

Cantor, Scott cantor.2 at osu.edu
Wed Oct 11 20:49:07 EDT 2017


On 10/11/17, 8:07 PM, "dev on behalf of Brent Putman" <dev-bounces at shibboleth.net on behalf of putmanb at georgetown.edu> wrote:

> It just isn't formally defined that way. It's a byte array. SHA1 might be the 99.9 % case in the real world (or maybe not if one
> considers the SourceID metadata extension), but it just sits very wrong with me.

I came to the same conclusion today but I can't recall what the thought process was back when the profile was drafted. It's certainly true that we had just stopped caring much about artifacts and that hasn't really changed much. If I thought artifacts were going to matter a lot, I would probably be drafting a new artifact type for us to use and it wouldn't have this problem because the entityID would be inside it.

-- Scott




More information about the dev mailing list