shibboleth discovery service

[Cantor, Scott]

> The location of each shared
> link is different, it’s impossible to define all of them in this SP’s metadata.

That isn't how discovery works, the link to the resource is not the returnURL, it has to be a dedicated location. If you want to use a standards-based DS anyway. But it's neither here nor there, if I'm not wrong then you can use something else that doesn't have this check, or change the code I guess. But I don't recommend taking code that's 6 months from EOL and deciding to own it by modifying it.

> What are the other alternatives to resolve this issue?

There are many centralized discovery tools around that are generally simpler to use than this old one is unless there's some inherent reason a Java servlet based version is valuable. Or there's running a Shibboleth SP plus the EDS as an option.

Or there's telling the vendor to provide for discovery as a condition for using their product. Crazy, I know.

-- Scott