Specify SP target URL to previous page (referer)
Cantor, Scott
cantor.2 at osu.edu
Mon Dec 1 10:50:08 EST 2014
On 12/1/14, 3:42 PM, "Jehan Procaccia" <Jehan.Procaccia at it-sudparis.eu>
wrote:
>by relative you mean a target like this ? (using a relative path)
>
>&target=../../opac-detail.pl?biblionumber=84779
No, I mean a relative URL starting from the root.
>If there is no application session cookie already set (anonymous
>browsing) , the application sends the user to a intermediary login page,
>the login button ( NativeSPSessionInitiator) containing :
>
>https://catalogue.mines-telecom.fr/Shibboleth.sso/Login?providerId=https:/
>/idp.tem-tsp.eu/idp/shibboleth&target=https://catalogue.mines-telecom.fr/c
>gi-bin/koha/opac-user.pl
It sounds like the problem is the application is broken, so I guess that's
the problem that has to be fixed. If it was integrated improperly, then
it's got a bug to fix.
>can the target be something like &target=$referer !?
No, as I said.
If you can control that SessionInitiator location, then point it at your
own script and use that to pick up the Referrer and create a new redirect
to the real SessionInitiator. If you can't, then you could even set a
discoveryURL to point it to your own script, have that pick up the
Referrer, and then redirect back with the entityID set. Etc. Many options.
If you can't do any of that, you have nowhere near enough access to this
to fix such a broken application.
-- Scott
More information about the users
mailing list