A cleaner way to prefetch MDQ metadata?

Wessel, Keith kwessel at illinois.edu
Mon Jun 27 20:16:20 UTC 2022

Very true. I often refer to that as a poor man's discovery, but it sure works. And if you don't want the user to have to select each time, get a little fancier with that page and have it set a cookie. Then, you can just use MDQ. I'll offer this up to them.


-----Original Message-----
From: Cantor, Scott <cantor.2 at osu.edu> 
Sent: Monday, June 27, 2022 3:13 PM
To: Shib Users <users at shibboleth.net>
Cc: Wessel, Keith <kwessel at illinois.edu>
Subject: Re: A cleaner way to prefetch MDQ metadata?

On 6/27/22, 4:08 PM, "users on behalf of Wessel, Keith via users" <users-bounces at shibboleth.net on behalf of users at shibboleth.net> wrote:

>    I think I’ll stick with the InCommon prefetch route even though I 
> know that’s cheating and not really using MDQ in a true dynamic 
> fashion until I can put something comprehensive and modular together. It’s not ideal, but it’s better in the short term than showing my SP operators how to configure even more pieces.

I guess my point is, you can't be expecting somebody to generate 100 or more elements here, right? If you had that many, obviously it would be a huge problem, but if you don't and it's just 10 or something, why do you need anything at all? Just stick them in a list box on a web page. Remember you don't really need the metadata to do discovery, you just need the name and the entityID, and hardcoding that makes more sense than anything else when the number is low.

-- Scott

More information about the users mailing list