session initiator / wayf question

[Mike Flynn]

But this started after we did a data center move so I have to assume that the issue is on my side, no?


On Sunday, October 26, 2014 12:28 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:
 


On 10/26/14, 2:44 PM, "Mike Flynn" <shibbolethlynda at yahoo.com> wrote:

>Here is one:
>
>ProQuest
> - Sign In 
><https://shib.lynda.com/Shibboleth.sso/InCommon?providerId=https://www.okt
>a.com/kn2f4wn9UYYBSSGGIHDI&target=https://shib.lynda.com/InCommon>

The protected resource is https://shib.lynda.com/InCommon, so when they
get back to that spot after the POST, they're not sending the cookie back
or it's not usable.

Note that you are preventing anybody from using SAML 2 if it falls into
the discovery step. It's using the old WAYF handoff that only works with
legacy Shibboleth protocol.


-- Scott

-- 
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20141026/54b27225/attachment.html