errors from our SP

Spencer Thomas Spencer.Thomas at
Tue Mar 3 10:17:50 EST 2020

Yes, we have had a discovery solution for a long time, partly because our users may use Shibboleth, Proxy servers, or other solutions for "off campus" access. We wanted a solution that would allow us to direct the user to whatever solution their campus provides, and so depending on metadata aggregates for those links is not sufficient. 

Spencer Thomas
Technical Architect / JSTOR and Artstor
ITHAKA <> / 301 E. Liberty St, Suite 250, Ann Arbor, MI 48104
Email: Spencer.Thomas at
Voicemail: 734-887-7004

On 3/3/20, 9:37 AM, "users on behalf of Cantor, Scott" <users-bounces at on behalf of cantor.2 at> wrote:

    On 3/3/20, 9:02 AM, "users on behalf of Spencer Thomas" <users-bounces at on behalf of Spencer.Thomas at> wrote:
    > We upgraded to the Shib 3 SP, and the symptom has gone away. As an added benefit, we are now able to use the
    > MDQ feed from the UK Federation, which has significantly reduced startup time.
    I imagine you have your own discovery solution; it might be useful to outline what that is, since that's typically the main barrier to getting the SP off the aggregates.
    -- Scott
    For Consortium Member technical support, see
    To unsubscribe from this list send an email to users-unsubscribe at

More information about the users mailing list