Issue with interoperability between ADFS 2016 and Shibboleth 2.4.4

[Peter Schober]

* d.alvarez2 <d.alvarez2 at miami.edu> [2017-11-27 14:49]:
> Correct, injecting the cookie does not work for active profile (apps in a
> smartphone) between ADFS 2016 (we upgraded from 2.0) and Shibboleth 2.4.4
> but it still works for the passive. 
> However, our current environment the cookie works for both active and
> passive (web) between ADFS 2.0 and Shibboleth 2.4.4.

It's neither the Shibboleth software /setting/ nor /evaluating/
(acting upon) those HTTP Cookies, AFAIU. So I'm not sure what you
expect from this group?

While such HTTP cookies (and infrastructure, such as network
appliances, proxies, load balancers, etc.) may influence whether/how
user agents access the Shibboleth IDP (or are being prevented from
doing so), Shibboleth itself knows nothing about it and as such cannot
have broken (or fixed) it.

The Shibboleth IDP doesn't implement what Microsoft calls "active"
flows so it cannot have changed or broken something here either.

To me all this means you'll need to be looking elsewhere, at the
places those HTTP Cookies are generated as well as evaluated.

-peter