AW: Error using CAS & Shibboleth

[Alex Olson]

Thank you for the help! We are using a 2.X version of shibboleth and I realize it's soon to be deprecated but I'd like to get it working anyway if only to better understand the process.


So I spent some time and further debugged the issue.


We have a production instance of shibboleth and a stage instance. They both talk to the same CAS instance & both use the same version of unicon's shib cas authenticator https://github.com/Unicon/shib-cas-authenticator.


Our production shibboleth instance works from top to bottom when tested via https://sp.testshib.org/

Our stage shibboleth instance fails upon POSTing to <https://sp.testshib.org/Shibboleth.sso/SAML2/POST> https://sp.testshib.org/Shibboleth.sso/SAML2/POST.


The only difference between the two request flows as far as I can see is that on our stage instance, the '_idp_session' cookie is NOT being set while it is set just fine on our production instance.


With this additional information are there any common reasons for an _idp_session_ cookie NOT to be set?


Thanks!?


---
Alex K. Olson
________________________________
Von: users-bounces at shibboleth.net <users-bounces at shibboleth.net> im Auftrag von Marvin Addison <marvin.addison at gmail.com>
Gesendet: Freitag, 28. November 2014 09:03
An: Shib Users
Betreff: Re: Error using CAS & Shibboleth

The best choice would probably be to start playing with the 3.0 beta and
the CAS implementation there if you can tolerate a lack of documentation.

I have a TODO for documentation in the coming weeks. If you're interested in the CAS protocol support in 3.0, I'd be happy to work with you to get it configured.

M<mailto:users-unsubscribe at shibboleth.net>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20141201/d9f337f0/attachment.html