Office365 ECP broken after shib3 upgrade

[Ryan Suarez]

From: users <users-bounces at shibboleth.net<mailto:users-bounces at shibboleth.net>> on behalf of "Klingenstein, Nate" <nklingenstein at calstate.edu<mailto:nklingenstein at calstate.edu>>
Reply-To: Shib Users <users at shibboleth.net<mailto:users at shibboleth.net>>
Date: Tuesday, October 18, 2016 at 9:41 AM
To: Shib Users <users at shibboleth.net<mailto:users at shibboleth.net>>
Subject: Re: Office365 ECP broken after shib3 upgrade

Has nothing to do with credentials, and there's no way you could have tested this without actually deploying V3. MS' proxy is going to contact whatever IdP it's told to contact, there's no way to control that locally in a controlled way.

There are many upgrades that have used a dedicated testing domain.

I was testing by deploying V3 in our dev/qa environment.  They are behind F5 load balancers so I can quickly switch between V2 and V3 by adding/removing them to the pool.

I’d switch to the V2 pool and confirm it works and then switch to V3, quit the outlook client, and start it up again.  There were instances that I saw the outlook client still connect with V3.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20161018/2f2b1c91/attachment-0001.html>