OpenAthens SP to Shibboleth (using OA Federation): Deep Links

[Nate Klingenstein]

Manoj,

I don’t think so.  There are only a few unlikely ways you could have made a mistake using application elements or bad cookie properties, but they’re not the first things I would investigate.

Instead, it sounds like the identity provider is not faithfully relaying back the RelayState sent in the original AuthnRequest back to the SP.  There’s not much to be done about that as an SP other than fixing the IdP; Scott may know of a trick around it, but there could be implications to decoupling the AuthnRequest from the inbound Response to such an extent.

Take care,
Nate.

> On Jan 26, 2016, at 08:52, Manoj Kancharla <manojk at silverchair.com> wrote:
> 
> Hi Nate,
>  
> Yes, here is an example in our context: he user clicks on “Sign in via OpenAthens” link from an article page. I’m doing a redirect to the Shibboleth handler like this: https://{0}/Shibboleth.sso/Login?entityID={1}&target={2} , where {0) = hostname, {1}=genericEntityID (OA), and {2}=the Url of the page from where the user initiated the login.
> 
> What’s happening now is that user is taken to the Athens Authentication Point and (after sign in) user is taken back to the home page : https://{0}/index.aspx <https://%7b0%7d/index.aspx> (instead of the article page)
>  
> Am I missing something in terms of configuration or other wise?
>  
>  
> Thanks
> 
> Manoj
>  
> From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Nate Klingenstein
> Sent: Tuesday, January 26, 2016 10:45 AM
> To: Shib Users
> Subject: Re: OpenAthens SP to Shibboleth (using OA Federation): Deep Links
>  
> Manoj, 
>  
> Do you mean that if the user were accessing:
>  
> https://vendor.com/stuff/secured/file.pdf <https://vendor.com/stuff/secured/file.pdf>
>  
> that the SP is capable of intercepting that request, recording the intended destination URL, sending the user home to authenticate, grabbing the user when they come back, and passing them to the intended destination URL after parsing the inbound token instead of just leaving them at https://vendor.com/home.html? <https://vendor.com/home.html?>  If so, then that’s exactly how it normally works.
>  
> If you meant other things, the answer may still probably require no specific configuration.  There’s lots of ways to do this stuff.
>  
> Take care,
> Nate.
>  
> On Jan 26, 2016, at 08:29, Manoj Kancharla <manojk at silverchair.com <mailto:manojk at silverchair.com>> wrote:
>  
> We’re currently in the process of migrating three of our customers from OpenAthens SP to Shibboleth using OA Federation. For one of the clients, there will be users signing in via OpenAthens and some will be signing via UK Federation (Shib)
> For the OA implementation, we need to implement deep links. Is there anything that needs to be configured differently (in Shibboleth2.xml) for the deep links to work?
>  
> Thanks
>  
> Manoj Kancharla
> Senior Software Developer | Silverchair Information Systems
> Email: manojk at silverchair.com <mailto:manojk at silverchair.com>
> Skype: manoj.kancharla1
>  
> -- 
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net <mailto:users-unsubscribe at shibboleth.net>
>  
> -- 
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net <mailto:users-unsubscribe at shibboleth.net>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160126/065e01d1/attachment.html>