ContentSetting discoveryURL

Cantor, Scott cantor.2 at
Tue Feb 25 09:54:48 EST 2020

> They have to be mutually correct or incorrect, they come from the same place.

Actually, that's false. So that's the problem. If you're initiating sessions by hand with a redirect, it's only pulling the discoveryURL from the low level configuration OR from the query string as a parameter.

So I'm guessing that's what you're doing. Add the URL to the redirect if it actualy varies by resource and that should fix it.

I'll have to review whether there was a deliberate reason for that behavior.

Sorry for the misdirect, but I caught it quickly,
-- Scott

More information about the users mailing list