Target URL is lost using Discovery Service

Mihael Koep mihael.koep at
Tue Dec 1 04:43:25 EST 2015

Hi Scott,

Am 27.11.2015 um 17:46 schrieb Cantor, Scott:
> On 11/26/15, 6:01 AM, "users on behalf of Mihael Koep" <users-bounces at on behalf of mihael.koep at> wrote:
>> I would be glad for any device how to solve or further debug the issue.
> Discovery doesn't break this feature, so you're going to have to talk to whoeever is running the DS and/or trace the traffic. Maybe you're mixing vhosts, http/https, etc. The SP works fine in that scenario, so the only person with the necessary access is you, unless your servers/link(s) are public.
> You could drop the relayState setting to see the actual URLs passed around, or just use cookies and then you can trace what it's dropping into them.
I installed the shibboleth EDS to ease my debugging and dropped the 
relayState setting as per your advice. I call the EDS with the URL

After selecting an IDP I can see the SAML-Request with SAML tracer and 
the RelayState

So at this point the target URL is already lost. Now my question is how 
does the relayState get populated or how can I influence its value?

Could it be a problem, that my entity id 
( does not match my SP hostname 

Many thanks in advance!

kind regards,
Mihael Koep

Mihael Koep | Softwareentwicklung
Softwareschneiderei GmbH | Gerwigstraße 10 | 76131 Karlsruhe | GERMANY
Registergericht: Amtsgericht Mannheim, HRB 109299
Geschäftsführer: Daniel Lindner
Tel.: +49 (0) 721 / 66 388 -08 | Fax.: +49 (0) 721 / 66 388 -09

More information about the users mailing list