You can skip using ADFS all together, like you said before you already have
shib and CAS talking. Just read the outline from microsoft to setup Shibboleth
I linked a few emails ago, going from OWA > ADFS > SHIB > CAS is un-necessary.
Would just be OWA > SHIB > CAS, it is almost immediate and us
If your CAS service is deployed with SSL and has certs, you might have to
deploy those certs on the hosts from where you connect to CAS (your service
which is now connecting and using cas)
On Dec 6, 2012, at 2:09 PM, chris marx wrote:
> I've configured my app to use our cas service, it also pul
Yeah we are using ADFS and I think is that where the hang-up is occurring. Our
consultant was going to use the documentation from the original post (
http://technet.microsoft.com/en-us/library/jj205456.aspx) but for some reason
when he had a conversation with a person at MS, he was told that was
Ahh.. OK. Yea you left out the ADFS bits.. :-)
My main point was if you/Laura were thinking Shib would be yet another
point for end users to 'login to', that would be incorrect. Shib and CAS work
nicely together to avoid just such a scenario.
--
thanks
kevin.foote
On Thu, 6 Dec 2012, Ga
Hey Kevin,
I guess the point is we are an ADFS school, not Shib, and have been for several
years. I probably also assumed that Laura was trying to use ADFS as that is
what MS tends to push.
My goal was to connect the two different SSO services (CAS and ADFS) and still
retain the ability to fed
On Wed, 5 Dec 2012, Gasper, John wrote:
-> EWU is just about to go live with O365, so we had a similar need, but
because we didn't want to have 2 un-connected single sign-on solutions we took
a different approach.
John, you are thinking about this wrong. As Jason mentioned before, user never
kn
Hi all,
I tried using a network sniffer in my machine to check if the logout
request is actually received.
It turns out it is, or at least I think so. Here's the sniffer output I
get, the package is sent from CAS Server's host to app2's host on the right
port (8080).
HTTP POST /app2 HTTP/1.1 (ap
Hi,
I have a service (wireless controller). Basically we want to integrate CAS
SSO with wireless hotspot captive portal. Wireless controller sends few
attributes in url such as switchip, mac, clientip etc therefore our login
url in address bar looks like this:
https://ourorganization/sso/login?cm
